Zoltan Kochan
e7b3e6ca45
Three small cleanups flagged on #11837: 1. `install_with_fresh_lockfile.rs` — the `drop(resolver); drop(npm_resolver);` block didn't actually free the resolver-side caches because the local `meta_cache`, `fetch_locker`, and `picked_manifest_cache` `Arc` bindings each still held one strong reference of their own. Drop those bindings explicitly too so the cache shrinks before the install pass starts pulling tarballs. 2. `resolve_dependency_tree.rs` — the doc comment on `resolve_dependency_tree` said later visitors "skip the recursion," but the `Some(existing)` branch only AND-folds the `optional` flag and the code then unconditionally allocates a fresh `DependenciesTreeNode` and recurses on the children. Reword the comment to match what the code actually does (only the `ResolvedPackage` envelope is shared). 3. `npm_resolver.rs` — `build_resolve_result` had 9 positional arguments under `#[allow(clippy::too_many_arguments)]`. Drop the suppression and take a `BuildResolveResult` struct instead so the three call sites read as named-field literals and adding a future field doesn't require touching every caller.
简体中文 | 日本語 | 한국어 | 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.
- 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:
