Zoltan KochanandClaude Opus 5
1e3bbf9622
pnpm v11 validates every `peerDependencies` value before resolving, via `validatePeerDependencies` at the top of `toResolveImporter`, and throws `ERR_PNPM_INVALID_PEER_DEPENDENCY_SPECIFICATION` when a value is neither a semver range, a `workspace:`/`catalog:` spec, nor a scheme-carrying specifier. The predicate was ported to pacquet as `is_acceptable_peer_spec` and unit-tested, but no production code ever called it, and the error code appeared nowhere in the Rust tree. The consequence was worse than a missing error. With `autoInstallPeers` on by default, `hoist_peers` copies an unsatisfied peer's raw specifier into the importer's dependencies. A typo like `"foo": "foo@1.2.3"` is not a range, so the resolver read it as a project-relative path and linked it, leaving `node_modules/foo` pointing at a directory that does not exist and recording the same link in the lockfile. The install reported success. Validation now runs from `ImporterHoistState::init`, the per-importer entry both `resolve_importer` and `resolve_workspace` funnel through, which is where v11 places it relative to resolution. The error is carried by a new `validate_peer_dependencies` module next to the existing `validate_dependency_alias`, and forwarded transparently through `ResolveImporterError` and `InstallWithFreshLockfileError` so the code and help text reach the CLI unchanged. The message and hint match v11 verbatim. A non-string value is skipped rather than reported: that is a malformed manifest, and the manifest parser answers for it. Closes pnpm/pnpm#14791. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_011dXMsoDXdrkju7zpCe8EYk
简体中文 | 日本語 | 한국어 | 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.