Zoltan Kochan
df3a09a05b
Share the materialization plan and the link phase between the two install paths, in `pacquet-deps-restorer`. The skip set decides what `node_modules` contains and the link phase decides how it is wired, so the paths diverging in either is a correctness bug rather than a style difference. `InstallFrozenLockfile::run` drops 875 -> 485. Sharing the link phase left one behavioural flag no test pinned, and tracing it found a real bug. A workspace package matching `publicHoistPattern` is recorded in the hoist result's `hoisted_workspace_aliases`, not `publicly_hoisted_aliases_with_bins`, which is all the post-build top-level bin link reads. Its bin therefore reached the root `.bin` only via the link phase's `node_modules` re-walk, which only a non-frozen install performed, so `--frozen-lockfile` left the shim missing. pnpm's headless path re-walks, so this was pacquet diverging. Both paths now re-walk, which fixes the gap and removes the flag. That surfaced a second latent bug: `link_bins::read_package` treated anything but a missing manifest as fatal, so a stray file in `node_modules` failed the install with `NotADirectory`. Non-directory entries now mean "not a package". Seven genuine differences stay as caller-side inputs, including the frozen path's non-empty-snapshots guard, which is load-bearing because `any_installability_constraint` short-circuits on `packages` before reading snapshots.
简体中文 | 日本語 | 한국어 | 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.