3067e4f6b4
The npm-resolver memoizes its metadata fetch for the whole resolution phase and clears it only once, via clearResolutionCache(), after resolution ends. Each memoized FetchMetadataResult carried jsonText, the raw registry response body kept only to mirror the response to disk without re-serializing meta. With an unbounded memo cache living for the entire phase, every raw body stayed resident until the end. On large cold-cache graphs that fetch full metadata (minimumReleaseAge / trustPolicy) these bodies reached hundreds of MB and OOM-killed 3GB CI runners. v10 did not keep the raw text on the memoized result, so this was a v10-to-v11 regression. Enforce the invariant at the cache boundary: the memoized fetch (memoizeFetchMetadata, replacing p-memoize, which has no hook between compute and store) caches a body-less shallow clone of each result, so jsonText reaches only the caller that initiated the fetch — the one that writes the disk mirror — and dies with that call. The cache is structurally incapable of pinning a body regardless of who consumes the fetch. Peak RSS drops by ~30% (back to the v10 level) with a byte-identical lockfile. Cache-hit callers see jsonText undefined and fall back to JSON.stringify(meta) in prepareJsonForDisk, which is functionally equivalent because loadMeta re-derives etag from the headers line on read. The replacement preserves p-memoize's semantics: in-flight dedup, eviction of rejections, and cache clearing. Follows the projection applied to the verifier caches in pnpm/pnpm#11878. Closes pnpm/pnpm#12868.
简体中文 | 日本語 | 한국어 | 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.