Zoltan Kochan
a5effe488d
The Rust CLI computed peer-dependency issues during resolution and then dropped them on the floor: every call site passed `peer_issues_sink: None`, and the only other consumer was a `tracing::warn!` the reporter never shows. `strictPeerDependencies` was parsed and read by nothing. `pnpm dedupe` was the one command that said anything, via a lockfile walk of its own after the install. An install that resolves now ends by applying `peerDependencyRules` to the issues its resolution left behind and either warning once — the same line the TypeScript CLI's reporter prints — or failing with `ERR_PNPM_PEER_DEP_ISSUES` under `strictPeerDependencies`, after the artifacts are written, the way `ERR_PNPM_IGNORED_BUILDS` already does. Living at the shared install tail means `add`, `remove`, `update`, `dedupe`, and `--lockfile-only` all get it, matching where pnpm places the call in `_installInContext`. Dedupe's own walk goes away as redundant. An install that skips resolution — frozen, or an up-to-date lockfile — still reports nothing, in both stacks. That asymmetry with `dedupe` is the subject of pnpm/pnpm#14098 and is deliberate: peer issues are a byproduct of resolution, so whatever ran one reports them, and `pnpm peers check` is what answers for a tree nobody re-resolved. Recomputing them on the frozen path would put a second, independent implementation on the hot path of every CI install and trade an install-vs-dedupe disagreement for an install-vs-install one. A test in each stack pins the decision. The verdict is read off the resolved lockfile rather than off the resolver's own issue map, because pacquet's `ParentChain` is name-only and would render every "Wanted:" entry with an empty version. That makes the lockfile walk shared code, so it moves out of the `peers` command into a new `pnpm-deps-inspection-peers` crate alongside the rules filter and the issue renderer — pnpm's `peers-checker` and `peers-issues-renderer` packages. Closes pnpm/pnpm#14098.
简体中文 | 日本語 | 한국어 | 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.