mirror of
https://github.com/pnpm/pnpm.git
synced 2026-06-28 09:55:39 -04:00
69cfcb7417
The integrated-benchmark "Precompile benchmark revisions" step took ~14 minutes every run. Two causes: 1. The "Cache Rust builds" step cached the multi-GB `bench-work-env/*/pacquet/target` dirs under a 1-minute restore timeout. A restore that large never finished in 60s, so (with `continue-on-error`) the cache silently missed and every run built all four targets cold. 2. `pacquet@HEAD` and `pnpr@HEAD` resolve to the same commit but built in separate clones, compiling the `pacquet` binary twice (same for main). Cache the compiled binaries per *resolved commit* instead: - Orchestrator: a `--reuse-prebuilt-binaries` flag skips the clone + `cargo build` for a target whose output binary is already present (i.e. restored from cache). Targets are built pnpr-first; since a `pnpr@<rev>` build also produces the `pacquet` client binary, a same-revision `pacquet@<rev>` reuses it by copy rather than recompiling the commit. - Workflow: resolve the HEAD/main SHAs, then cache the two `pnpr@<rev>` binaries keyed on the commit (they cover all four targets via the dedup-copy). `main` is a near-certain hit on PRs (stable SHA) and a same-HEAD re-run hits HEAD too, so only a fresh HEAD compiles. Drop the giant `bench-work-env/*/pacquet/target` cache (the small binary caches restore in seconds, with no eviction risk) and keep a cargo-deps + orchestrator-target cache with a realistic 3-minute timeout. A fresh-HEAD run now compiles one workspace once (~half the old work); re-runs and main reuse cached binaries and skip compilation entirely.
简体中文 | 日本語 | 한국어 | 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:
License
MIT, except the pnpr/ directory, which is source-available under the PolyForm Shield License 1.0.0.