Zoltan KochanandClaude Opus 5
82299fd2c3
Cargo resolution offers the solver every non-yanked version on a crate's compatibility line, including prereleases outside the requirement that brought the crate in. Building the constraints for such a candidate failed outright when one of its dependencies had no non-yanked version in the index, so a whole solvable graph was rejected. Installing Rspack hit this through napi 3.0.0-beta.6, which needs `napi-build ^3.0.0-beta` while napi-build 3.0.0-beta.0 is yanked. A dependency the index cannot meet now maps to a `PackageKey` of its own that no version is ever registered under. The solver treats the candidate that needs it as a plain incompatibility, backtracks past it, and names it in the report when nothing else resolves. That replaces the early-return skip for a dependency naming a crate the index does not carry, which lost the reason for the dead end. Feature unification walks the selected graph with a wider feature set than the solve used, so it can reach a dependency no version meets too. It now skips that dependency and lets the next round rule the candidate out, and the graph validation that follows treats it as a solution to retry rather than an error. Closes pnpm/pnpm#14952 Co-authored-by: Claude Opus 5 (1M context) <noreply@anthropic.com>
简体中文 | 日本語 | 한국어 | 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.