Zoltan Kochan
bd26366c79
A registry version that carried no `dist.integrity` was recorded in the lockfile with a bare tarball URL and no hash, and `--lockfile-only` never computed one — so the very first `pnpm install --frozen-lockfile` over that lockfile failed with `ERR_PNPM_MISSING_TARBALL_INTEGRITY`. Two independent gaps produced it, and both are closed here. First, `dist.shasum` was ignored. pnpm's `getIntegrity` promotes the legacy hex digest to a `sha1-` SRI string when `dist.integrity` is absent, which is what pins every version published before subresource integrity — the whole of `https://node-registry.bit.cloud/`, for one. pacquet parsed the field and dropped it, leaving those versions unpinned and diverging from the lockfile the TypeScript CLI writes for the same graph. `dist_integrity` now mirrors `getIntegrity`, including the `ERR_PNPM_INVALID_TARBALL_INTEGRITY` failure for a shasum that is not a hex digest. It also restores the stronger of the two behaviours: a registry-published hash pins the bytes, where hashing whatever arrived pins nothing. Second, `--lockfile-only` skipped the `PrefetchingResolver` wholesale, and that wrapper owns `populate_missing_integrity` — the only path that hashes a tarball no registry hash covers. Background prefetching and integrity completion are now separate concerns: the wrapper always sits in the resolver chain, and `prefetch_downloads` turns off only the speculative download. A run that materializes nothing (`--lockfile-only`) or only part of the graph (a filtered workspace selection) still fetches the few tarballs whose hash the lockfile cannot be written without, which is what pnpm does with `resolutionNeedsFetch` under `dryRun`. Closes pnpm/pnpm#13547
简体中文 | 日本語 | 한국어 | Italiano | Português Brasileiro
Fast, disk space efficient package manager:
- Fast. Up to 2x faster than the alternatives (see benchmark).
- Efficient. Files inside
node_modulesare linked from a single content-addressable storage. - Great for monorepos.
- Strict. A package can access only dependencies that are specified in its
package.json. - Deterministic. Has a lockfile called
pnpm-lock.yaml. - Works as a Node.js version manager. See pnpm runtime.
- Works everywhere. Supports Windows, Linux, and macOS.
- Battle-tested. Used in production by teams of all sizes since 2016.
- Experimental Rust port. Includes pacquet, an experimental port of the CLI written in Rust.
- See the full feature comparison with npm and Yarn.
To quote the Rush team:
Microsoft uses pnpm in Rush repos with hundreds of projects and hundreds of PRs per day, and we’ve found it to be very fast and reliable.
Platinum Sponsors
|
|
Gold Sponsors
|
|
|
|
|
|
|
|
Silver Sponsors
|
|
|
|
|
|
|
|
|
| ⏱️ Time.now |
Support this project by becoming a sponsor.
Background
pnpm uses a content-addressable filesystem to store all files from all module directories on a disk. When using npm, if you have 100 projects using lodash, you will have 100 copies of lodash on disk. With pnpm, lodash will be stored in a content-addressable storage, so:
- If you depend on different versions of lodash, only the files that differ are added to the store.
If lodash has 100 files, and a new version has a change only in one of those files,
pnpm updatewill only add 1 new file to the storage. - All the files are saved in a single place on the disk. When packages are installed, their files are linked from that single place consuming no additional disk space. Linking is performed using either hard-links or reflinks (copy-on-write).
As a result, you save gigabytes of space on your disk and you have a lot faster installations!
If you'd like more details about the unique node_modules structure that pnpm creates and
why it works fine with the Node.js ecosystem, read this small article: Flat node_modules is not the only way.
💖 Like this project? Let people know with a tweet
Getting Started
Benchmark
pnpm is up to 2x faster than npm and Yarn classic. See all benchmarks here.
Benchmarks on an app with lots of dependencies:
License
MIT, except the pnpr/ directory, which is source-available under the PolyForm Shield License 1.0.0.