Nicolas Charpentier
0b4ebcfef9
Resolution re-derived the same data once per dependency edge instead of once per packument: - filterPkgMetadataByPublishDate ran on every pick (every edge) with minimumReleaseAge active — the default since it is 1440 min — parsing a Date per version and rebuilding the versions map each time. It is now memoized per packument object in a WeakMap, keyed by cutoff and trusted versions so one packument served under different policies still filters per policy. Sharing the returned object is safe: callers already shared the inner version manifests, and the packument objects the resolver passes in are themselves cached and treated as read-only. - pickPackageFromMeta re-parsed version strings and ranges on every satisfies/maxSatisfying call. Parsed SemVer and Range instances are now cached in capped Maps (cleared at 50k entries so long-lived processes cannot grow them without bound), and maxSatisfying/ minSatisfying are replaced with loops that reuse the caches. The dist-tag repopulation loop in the publish-date filter likewise compares already-parsed instances instead of calling semver.gt on strings. - Concurrent offline picks of one package all miss the pre-queue in-memory cache check, then each re-read and re-parsed the mirror behind the per-package limiter (176 of 1311 loads on the benchmark fixture were duplicates). The limiter callback now re-checks the cache; offline entries are always disk-sourced, so this is equivalent to arriving after the first caller cached it. - clearMeta condensed every version object through ramda's curried pick; a direct field loop does the same with no per-field dispatch. The presence check via undefined-comparison matches the previous behavior because version objects come from JSON, which cannot encode undefined. Resolution of the 1246-package benchmark fixture is 12.5% faster on top of current main (4.27s -> 3.73s, hyperfine, offline hot cache); the resulting lockfile is byte-identical. Attribution: filter memoization -11%, semver caches -4%, the rest ~-1%.
简体中文 | 日本語 | 한국어 | 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.