Two installs of one workspace, same inputs and same binary, emitted different lockfiles: a peer suffix would bind `postcss@8.4.19` in one run and `8.5.25` in the next. https://github.com/pnpm/pnpm/pull/13584 removed most of it — 196 differing lines where there had been 10,390 — but not the last of it. Bisecting what varies between runs: the resolved package set and every package's children are identical, hash for hash. The occurrence nodes are not, ranging from 58,972 to 60,664 on a 114-importer workspace. Importers race for a package's children-ownership claim, and a walk holding the claim only transiently still leaves its occurrence nodes in the shared tree; how many it leaves depends on the interleaving. Occurrence identity feeds peer-variant computation, so that is enough to move a binding. Resolve the initial waves one importer at a time, boxing each so the enclosing install future does not grow by a wave's frame. Eight consecutive replays of that workspace now emit byte-identical lockfiles, where before almost every pair differed, and the result matches one of the two lockfiles the concurrent path was alternating between — no resolution changes, the choice simply stops depending on scheduling. It is also faster wherever it was measured, because the races cost redundant subtree walks: that workspace resolves in ~9.3s against ~10.3s, a cold install over a 50ms link takes 2.64s against 2.72s, and the resolution fixtures are unchanged. The waves overlapped resolver waits, but pacquet dedups those through the workspace-wide wanted-dep cache, so there was less to overlap than the fan-out assumed. Closes https://github.com/pnpm/pnpm/issues/13567.
jsr: and named-registry package names (empty scope/name, path separators) (#12677)
简体中文 | 日本語 | 한국어 | 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.