Aquesta és una versió anterior. La versió actual és la 12.15.0. pnpm 12.15.0 · Data de publicació:
11.0.8 forma part de la branca 11, que té suport fins al 30 d’abril del 2027. endoflife.date
Fitxers d’instal·lació 11.0.8
| Arquitectura | Tipus | Àmbit | Mida del fitxer | Baixa | SHA256 |
|---|---|---|---|---|---|
| 64 bits | ZIP → Portable | — | — | github.com | VirusTotal |
| ARM64 | ZIP → Portable | — | — | github.com | VirusTotal |
L’enllaç i l’SHA256 provenen del manifest comunitari del Gestor de paquets del Windows. Convé comparar el hash del fitxer baixat abans d’executar-lo.
Notes de la versió
> See full v11.0.0 changelog: https://github.com/pnpm/pnpm/releases/tag/v11.0.0
> Migration guide: Migrating from v10 to v11
## Patch Changes
- Restored the heuristic that preserves tarball URLs in `pnpm-lock.yaml` when they cannot be derived
from name+version+registry, even with the default `lockfileIncludeTarballUrl: false`. Without this,
`pnpm install --frozen-lockfile` from an empty store fails with ERR_PNPM_FETCH_404 for packages on
registries that serve tarballs from a non-standard path — most notably GitHub Packages
(`https://npm.pkg.github.com/download/<scope>/<name>/<version>/<hash>`) and JSR.
`lockfileIncludeTarballUrl: true` continues to force the URL into the lockfile for every package
#11276.
- Run `preversion`, `version`, and `postversion` lifecycle scripts for `pnpm version`.
- Fixed `ERR_PNPM_BAD_TARBALL_SIZE` when a registry serves tarballs with an end-to-end `Content-Encoding`
(e.g. `gzip`). Tarballs are already compressed, so the fetcher now requests them with `Accept-Encoding:
identity` (matching pnpm v10's effective behavior) and, as defense in depth against misbehaving
servers, no longer enforces the strict `Content-Length` check when the response declares a
`Content-Encoding` — `Content-Length` in that case refers to the encoded payload, not the decoded
bytes the fetch implementation yields #11506.
