Zoltan Kochan
39cd88ac8e
`cargo` lets semver-incompatible versions of a crate coexist, so the resolver shards a crate by compatibility line: pubgrub picks one version per package, and a line is what "one version" means here. The line a dependency resolved against was chosen eagerly, from the newest version meeting the requirement, and the solver only ever saw that one. A requirement spanning several lines, such as `>=1, <3`, was therefore pinned to the newest before solving began, and a dead end there failed the whole resolution although an older line resolved. `cargo` backtracks and picks the older version. A requirement met on more than one line now resolves through a choice package of its own, whose versions are the newest version on each line and which depends on the line that version names. pubgrub reaches for the largest version first, so the newest line is tried first and an older one is reached by ordinary backtracking, which is `cargo`'s heuristic. A requirement met on a single line still names that line directly, so nothing changes for the ranges almost every manifest writes. Index discovery widens to match: every line a requirement admits can be selected, so the versions on each are walked and what they need is fetched. Feature selections are folded into every admissible line, since the solver may settle on any of them, while the graph is walked through the line it actually settled on. Checked against `cargo` itself on the real index. For a workspace asking for `rand >=0.6, <0.8.0` in one member and `rand 0.6` in another, both resolve to the same 28 packages, `rand` 0.6.5 and 0.7.3 among them. Closes pnpm/pnpm#14962
简体中文 | 日本語 | 한국어 | 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.