Trevor BurnhamandZoltan Kochan
2c82ea5a78
`--force` reaches the link phase with the previous install's `packages:` records withheld, and `package_content_changed` reads a missing current entry as "unchanged", so `SlotImportSource.force` came out false for every slot. `import_indexed_dir` then short-circuited on the `package.json` completion marker and left the earlier install's files in place: a package whose integrity changed kept its old contents while the lockfile recorded the new one, at exit 0 with no warning. Carry the reuse policy's `force` into that decision instead of inferring it from records `--force` itself withholds. Grouping the two `packages:` maps and the flag as `SlotReuse` gives the rule one home for the warm and cold batches and keeps `ColdBatch` within the field cap. Rule early materialization out under `--force` too. The link phase now replaces every slot, so slots populated during resolution would only be staged away again, which would have imported each package twice on the platforms where that optimization runs. Carry `.pnpm-needs-build` under a forced import as well. Replacing a slot's files restores the pristine base map, since the side-effects overlay is applied later by the build phase. Under the global virtual store that phase would otherwise read the re-imported files as a cache hit and skip the rebuild, leaving a built package reverted. The marker is what distinguishes a pristine re-import from a finished build, which is why an interrupted build already carries one. pnpm 11 is not affected. Its `forceImportPackage` is `!depIntegrityIsUnchanged`, and `isIntegrityEqual(resolution, undefined)` is false, so a withheld record makes it force the import rather than skip it. The Rust port drew the opposite conclusion from the same input. Closes pnpm/pnpm#15030 --------- Co-authored-by: Zoltan Kochan <z@kochan.io>
简体中文 | 日本語 | 한국어 | 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.