Zoltan Kochan
01dc5ac4c8
`getOutdatedLockfileSetting` names eleven fields whose drift makes the lockfile unreproducible; pacquet compared seven. A project that flipped `autoInstallPeers`, `dedupePeers`, or `excludeLinksFromLockfile` after writing its lockfile got a clean `--frozen-lockfile` install from pacquet and `ERR_PNPM_LOCKFILE_CONFIG_MISMATCH` from pnpm — the install proceeded against a lockfile whose recorded resolution no longer matched the settings that produced it. Each comparison follows pnpm's: `autoInstallPeers` and `excludeLinksFromLockfile` are checked only when the lockfile records a `settings` block, since one written before the field says nothing about it, while `dedupePeers` is written only while it is on, so an absent key reads as `false`. The fields are now compared in pnpm's order too. Only the first drifted field is reported, so the order decides which name a user sees, and `injectWorkspacePackages` sat where pnpm checks `autoInstallPeers`. `pnpmfileChecksum`, the eleventh field, is still unchecked: it needs the pnpmfile's hooks gate, which means loading the pnpmfile through the Node worker on a path that deliberately avoids it. Filed as pnpm/pnpm#13385. `check_lockfile_settings` takes the same options struct its catalog-aware twin took, and the twin is gone — the two had drifted into different field sets, which is what let the new fields be added to one and missed at the other's call site. Closes the error-code half of item 1 of pnpm/pnpm#13315.
简体中文 | 日本語 | 한국어 | 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.