Zoltan Kochan
fea49c1fd2
Walker::resolve_node was 549 lines — by a wide margin the largest function in the crate (next is resolve_node_seed at 321, the median is 13). Nesting was never the problem: real block depth peaks at 5, in the two-pass child loop that is legitimately nested. Length was, because eleven sequential phases shared one large local context. Lift the three phases that have clean seams into named helpers: - The graph-entry / NodeRecord capture moves to finalize.rs as Walker::record_walked_node, next to the post-walk passes that consume those records, taking a borrowed WalkedNode context. - Building the ParentRefs map descendants see — locked-peer scoping, provider children, locked pins — becomes Walker::build_child_parent_refs, returning the shared map, the node's own contribution, and whether anything changed. - The node's own peer resolution, its fold with the children's, and the depPath it renders to become Walker::resolve_node_peers. The early-return short-circuits (context-free depPath, cycle re-entry, fast cache hit, peersCache hit) stay inline: as Option<NodeOutput>-returning helpers they would make the control flow harder to follow, not easier. resolve_node is now 378 lines of linear short-circuits plus the child walk. No allocation, cloning, or traversal change. The extracted phases take borrowed context structs, following the CacheHitContext / DeferredChildContext precedent, so no borrow conflict is resolved with a clone. The one behavioral identity worth naming: resolve_node_peers folds the node's own resolved peers into auto_install_resolved_peers after its loop instead of during it — the two maps agree because resolve_one_peer only ever inserts under the peer name it was called for. Also fold in the adjacent micro-cleanup the issue called out: Walker::deferred_child_resolution did two pure_pkgs hash lookups where one if-let chain does. Closes pnpm/pnpm#13553.
简体中文 | 日本語 | 한국어 | 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.