Arthur FontaineandZoltan Kochan
08c5d80c26
The hoister collapses every peer variant of one package version onto a single node, keyed by the first snapshot key it sees for that version (pnpm/pnpm#14039 on the Rust side, `toTree`'s `depPathByPkgId` on the TypeScript side). Only that one key reaches the dep-graph walk, but the walk kept indexing locations by it and looking them up by the exact key each edge declares. Every edge on another variant missed. A workspace project that declared the losing variant lost its entry in `direct_dependencies_by_importer_id` and in `.package-map.json`, so under `nodePackageMapType: standard` it could not require a dependency it declares. A package that depended on one lost the child edge, and with it the `node_modules/.bin` link the child provides. Key the indexes — and the lookups — by the peer-suffix-free package id, which is the identity the hoister collapsed on: `pkg_locations_by_pkg_id` and `package_ids_by_pkg_id` in pacquet, `pkgLocationsByPkgId` in the TypeScript CLI. The two stacks derive the id the way their own hoister does: `PkgNameVerPeer::without_peer` there, `nameVerFromPkgSnapshot` here. The hoisted-linker regression test the original version of this PR added is kept, extended to assert the package map. --------- Co-authored-by: Zoltan Kochan <z@kochan.io>
简体中文 | 日本語 | 한국어 | 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.