Zoltan Kochan
1590aeb17c
pnpm's pre-command block calls syncEnvLockfile for every command that isn't in skipPackageManagerCheckForCommand, so a project pinning pnpm through devEngines.packageManager (or a v12+ packageManager field) gets its packageManagerDependencies recorded whatever the user ran. pacquet synced only from the install-family pipelines, so `pnpm list` in a fresh clone left no lockfile behind. pre_command_plan now returns a PreCommandPlan — either the version switch it already planned, or the env-lockfile sync it needs — and lib.rs runs whichever came back on the pre-command runtime. The sync is planned in the same two places pnpm reaches syncEnvLockfile: after checkPackageManager on the warn/error/corepack path, and on the download path when the running pnpm already satisfies the pin (where pnpm's switchCliVersion still resolves and saves before returning). The install family is excluded, because it passes its own frozen-lockfile value to the sync and pacquet — unlike pnpm — fails a frozen install whose packageManagerDependencies are out of date. Syncing those commands from the pre-command block would repair the lockfile before the pipeline could refuse to. Excluding them also keeps the up-to-date install fast path free of the lockfile read. The plan is skipped without touching the network whenever the env lockfile already records a version satisfying the pin. That answer needs the lockfile, but the download path has already read it looking for a version to switch to, and `pnpm-lock.yaml` is read whole — so the parsed lockfile is threaded into the sync decision rather than read a second time. A warm pinned project pays one lockfile read per command, the same as before. package_manager_to_sync now takes the effective pmOnFail rather than reading the manifest's own onFail, matching how pnpm resolves wantedPackageManager.onFail before shouldPersistLockfile sees it. Closes pnpm/pnpm#13348
简体中文 | 日本語 | 한국어 | 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.