mirror of
https://github.com/pnpm/pnpm.git
synced 2026-06-27 17:35:30 -04:00
83457b5764
Port yarn berry's popularity-based ident preference (buildPreferenceMap / getHoistIdentMap) into the real-hoist crate so that, when multiple versions of one name compete for the root node_modules slot, the most-used version wins — with the root's direct dependencies always preferred first. This matches pnpm's hoisted node-linker layout, which pacquet previously diverged from by hoisting the first-visited version. Mechanism: - build_hoist_ident_map / add_dependent / PreferenceEntry build a per-name list of candidate idents ordered most-preferred-first (root deps, then by the count of distinct dependents + peer-dependents, stable on ties). - A new AbsorbDecision::Defer plus is_preferred_ident gates free-slot absorption: only the currently-preferred ident may take a free root slot; a non-preferred version stays nested. - hoist_into_root performs a per-pass ident shift (VecDeque::pop_front) that promotes the next candidate when the preferred ident still hasn't reached the root, so a less-preferred version can land once the preferred one is proven unreachable. - HoistCtx bundles root, border_names, and the ident map to keep hoist_subtree within the argument limit. Tests: unit tests for the preference machinery and most-used-wins precedence, a dep-graph workspace test, and two frozen-lockfile CLI e2e tests (single-project and workspace) ported from installing/deps-restorer/test/index.ts. TEST_PORTING.md is updated accordingly. --------- Co-authored-by: Claude <noreply@anthropic.com> 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.
- 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.