Zoltan Kochan
a99b8526a0
The lockfile pinned `@types/node@26.1.2` as the hoisted optional peer of every `@inquirer/prompts` consumer, next to the `22.20.1` the workspace catalog pins with `^22.19.19`. That is the bug71a4934d3ffixed: `getHoistableOptionalPeers` used to maximize over every version in the graph instead of bounding its candidates by the workspace root's own specifier, so an optional peer declared as `*` pulled in the newest version any importer had resolved. The entries came in with7f81da30b8, six days after that fix landed, because the install that wrote them ran pnpm 12.0.0-alpha.21 — published before the fix — rather than the pinned 12.0.0-beta.2. Replaying that commit's inputs with alpha.21 reproduces its lockfile byte for byte, while beta.1, beta.2, and the TypeScript CLI at 11.18.0 all produce `22.20.1`. So every full re-resolution rewrites those 80 lines, and unrelated pull requests pick the correction up as soon as one of their manifest changes forces one — in pnpm/pnpm#13535 it accounts for most of the lockfile diff. Re-resolving here keeps it out of the next PR that touches a manifest. No product code changes: the resolver fix is already in.
简体中文 | 日本語 | 한국어 | 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.