Zoltan Kochan
d7d0ba7ec0
pnpm 12 rejected `pnpm peers check` — the spelling pnpm.io documents and pnpm's own dedupe output recommends — as an unexpected argument, and its `dedupe --check` failed with a bare "Lockfile would be modified by deduplication": no diff, no error code, no peer-dependency warning. `peers` now takes an optional subcommand: `check` (or nothing) runs the check, anything else prints the command's help and exits 1, mirroring the TypeScript handler. `dedupe --check` now renders what deduplication would rewrite, under pnpm's `ERR_PNPM_DEDUPE_CHECK_ISSUES`. The report reuses the lockfile diff behind `install --dry-run`, which grew per-alias detail for updated `snapshots:` entries and a key selector: `--dry-run` keeps comparing importers by manifest specifier, while `--check` compares them by resolved version, because deduplication rewrites peer-resolved versions without touching specifiers. Rendering goes through the archy tree renderer `list` and `why` already share, so the output matches pnpm's `renderDedupeCheckIssues`. A snapshot that no longer parses (an older lockfile format the run has just rewritten) degrades to no baseline rather than replacing the verdict with a parse error, and a text-only rewrite — drifted settings, a config dependency the run synced — says so instead of printing an empty report. Dedupe also emits pnpm's `Issues with peer dependencies found. Run "pnpm peers check" to list them.` warning. It is derived from the deduplicated lockfile through the same checker and `peerDependencyRules` filtering the `peers` command uses, so the warning and the command it recommends always agree, and it is gated like pnpm's install-time one: a bad peer, or a missing peer at least one parent requires non-optionally. `pnpm install` still does not warn — unlike dedupe it can finish without resolving, so that warning has to come from the resolver rather than a lockfile walk. The `licenses list` half of the issue was already fixed on main by pnpm/pnpm#13347. TypeScript CLI: no counterpart change — pnpm 11 already behaves this way. Closes pnpm/pnpm#13321
简体中文 | 日本語 | 한국어 | 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.