b065ea3eb7
The metadata mirror stored one JSON document per package, so every resolution parsed every version manifest of every packument it touched: 178MB of JSON for the 1246-package benchmark fixture, of which ~1% (the picked versions) was ever read. loadMeta was 23% of resolution CPU after pnpm/pnpm#13504. The Rust CLI already shipped an indexed mirror layout (headers record, index record with per-version byte spans, concatenated raw version fragments); the TypeScript CLI treated those mirrors as cache misses, so the two stacks thrashed a shared cache. Both CLIs now read and write the same layout under the format id pnpm-meta-v1, and the metadata cache directories move from v11 to v12 so a pnpm version that predates the layout never opens the files at all. The offline legacy-mirror hint now looks under v11, and pnpm cache prune removes the v11 roots. NDJSON remains the layout for filterMetadata documents and is still read as a fallback. Loading an indexed mirror parses only the two leading records and builds versions as enumerable parse-once getters over byte spans, so a manifest keeps one identity across filtered views and hook mutations. Corruption is treated like an unreadable mirror in both stacks: a fragment that does not parse throws a typed error, offline resolution fails with NO_OFFLINE_META, the disk fast paths fall through to the network (only for errors attributable to the disk copy), and a 304 over a damaged file escalates to a cache-bypassing refetch that rewrites the mirror — otherwise the intact etag would keep 304-validating a poisoned file forever. The declared headers length is bounded, the encoded mirror form is memoized per fetch result so workspace projects sharing one in-flight fetch do not each serialize a copy, and cache view reads through the shared loader in both CLIs. Resolution of the 1246-package fixture is 16% faster on a warm mirror (3.82s -> 3.21s, interleaved paired runs, offline); the resulting lockfile is byte-identical across old-format, new-format, and mixed-format configurations. --------- Co-authored-by: Zoltan Kochan <z@kochan.io> Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
简体中文 | 日本語 | 한국어 | 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.