73707d2ecb
Two published v11 releases were broken in ways nothing in the pipeline checked, and both only surfaced once users upgraded onto them. 11.12.0 was packed by a pnpm that ignores the .pnpmfile.cjs beforePacking hook, so the bundled dependency fields survived into the published manifest. Resolving node-gyp then pulled a peer-suffixed snapshot into the env lockfile, and every upgrade onto 11.12.0 died in buildLockfileFromEnvLockfile (pnpm/pnpm#12955, pnpm/pnpm#12959). 11.12.0 and 11.13.0 also shipped `@pnpm/exe` platform packages with no native binary; setup.js exits 0 when the binary is missing, so the placeholder bin survived and only a real invocation caught it. Assert on the packed tarball that the published pnpm manifest declares no dependency fields, rather than trusting either stripper, since npm publishes are immutable. Then, in the Tag workflow, upgrade from the release line's current version onto the new one for both the `pnpm` and `@pnpm/exe` wrappers and run the resulting binary. The release workflow has already published under next-<major> at that point, so this reads the real registry artifact, and it runs before the dist-tags move — the last gate before a version reaches everyone. Verified against the registry: the assert rejects pnpm@11.12.0 and accepts 11.11.0/11.13.1; the upgrade gate passes 11.13.0 -> 11.13.1 and catches both `pnpm@11.12.0` and `@pnpm/exe@11.12.0`/11.13.0. Related to pnpm/pnpm#12959.
简体中文 | 日本語 | 한국어 | 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.