Zoltan Kochan
fc0278acd7
Three ways a project's `packageManagerDependencies` entry could be rejected by `--frozen-lockfile` while agreeing with the manifest, each leaving a plain install reporting success without repairing anything. A bootstrap repair — entries whose resolutions the bootstrap refuses to read are discarded and re-resolved before the pinned pnpm is installed — went through the same save path as a genuine update. It now resolves in memory under a frozen lockfile and leaves the lockfile untouched, and re-resolves the version the lockfile records rather than the range around it, so the command runs the pnpm the lockfile pins. `resolve_package_manager_integrities` returns the env lockfile it resolved, which `install_engine_to_store` installs from instead of re-reading the one it just wrote, and the switch plan carries the locked version. `switchCliVersion` does the same on the TypeScript side by dropping `save` and passing the locked `pmVersion`. `exact_version` kept the `+<algorithm>.<hash>` build corepack appends. A `devEngines.packageManager` version carrying one was recorded as the version to look for, but the registry resolves that spec without the build, so the recorded `version` never equalled it: the entry was rewritten byte-for-byte on every install and rejected on every frozen one. The build is now dropped where the pinned version is read, as `parse_package_manager` already does for the `packageManager` field; the `specifier` still records the pin as the manifest writes it, which is what the TypeScript CLI writes. The up-to-date fast path returns before the install pipeline, which is where the install family records the pin — the pre-command block defers to it. A pin added to a project whose dependencies are already installed therefore never reached the lockfile. The fast path now gives way when the pin still has to be recorded, and stays a fast path once it is. The TypeScript CLI records the pin from its pre-command block and compares versions with semver, so the last two divergences are Rust-only. Related to pnpm/pnpm#14124.
简体中文 | 日本語 | 한국어 | 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.