76fa59584e
With nodeLinker: hoisted and autoInstallPeers: false, a package that two workspace projects use with different peer versions got only one copy, so the second project resolved the first project's peer. pnpm v11 nests the second variant; this was a v12-only regression. The hoister now keeps a peer-bearing node's own snapshot key as its reference. A node without peer names still collapses onto the first-seen variant, as pnpm v11's depPathByPkgId does, which keeps peer-variant-heavy lockfiles from exploding the per-path walk. When autoInstallPeers is on, peer names are empty and every variant collapses as before. The hoisted dep-graph walk indexes package locations by exact snapshot key as well as by package id. Importer direct dependencies and child edges resolve to their own variant's copy first, then fall back to the package id for variants the hoister collapsed. Keeping the collapse and adding yarn's peer check to the hoister's dedup path also places the copies correctly, but the walker then sees two copies with one snapshot key. The hoisted linker treats those as duplicates, builds one, and symlinks the other, which cross-links the variants again. On a large real lockfile with autoInstallPeers off, the hoisted tree grows from 8358 to 17157 nodes. The yarn-parity alternative produces 17570, so the growth is the copies peer resolution requires. Closes pnpm/pnpm#17395 --------- 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.
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.