91fb66344c
The auto-install-peers hoist loop cloned the workspace tree and ran a full peer pass - DependenciesGraph construction included - once per importer per round, making a from-scratch resolve of a large component workspace quadratic in both time and memory (the regression Bit hit through the napi engine). Replace the per-round snapshot + full pass with a PeerHoistDiscovery engine shared by every hoist round of one workspace resolve: - discovery walks share one persistent tree view, incrementally synced from the workspace context; a children-ownership handover that rewrites existing occurrence nodes (tracked by a rewrite counter), a re-recorded child list, or a changed peer split discards the whole view instead of merging; - the walker's purePkgs / peersCache / parent-context maps persist across rounds and importers, so a subtree settled by one importer's pass short-circuits every compatible revisit - the same sharing the final resolve_peers_workspace pass already applies within one call; - discovery skips graph construction entirely: the hoist loop only consumes missing peers and resolved providers, and each peers-cache item carries its subtree's per-package missing breakdown so the owner-scope report stays exact under cross-round cache hits. Also drop the remaining per-importer O(workspace) costs in the initial barrier: record_first_walk_missing no longer deep-clones the children-owner map, the preferred-versions fold reads an append-only resolved-versions log through a per-importer cursor, and the owner-scope maps are snapshotted once per barrier. The CLI deploy tests' stderr assertions are also made robust to miette's path-length-dependent line wrapping. cargo bench -p pacquet-resolving-deps-resolver --bench workspace_full_resolution (331 importers, 5,000 shared packages, peer hoisting, no lockfile): before 65.1s / 3.76 GiB peak RSS; after 1.55s / 1.14 GiB.
简体中文 | 日本語 | 한국어 | 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.