dbf347bf5e
run:
- A failing `test` script now prints "[ELIFECYCLE] Test failed. See above
for more details." instead of the generic exit-code line, matching
pnpm's reportLifecycleError test special-case (reportError.ts:371-378).
- Empty script bodies are skipped in run_stage, matching pnpm's
`!m.scripts[stage]` no-op (runLifecycleHook.ts:100) and the truthiness
gate on pre/post hooks (run.ts:403,411).
dlx:
- Build a fresh build-script allow-list for the cache install (the dlx
packages' aliases + CLI --allow-build) instead of inheriting the
caller project's allow_builds / dangerously_allow_all_builds. Mirrors
pnpm's `allowBuilds = {...resolvedPkgAliases, ...allowBuild}`
(dlx.ts:168). This also makes the cache key (which hashes only pkgs +
CLI allow_build) fully capture the effective build policy.
- Select the default bin among many by the installed package's own
`name` field (scopeless), not the dependency alias it was installed
under — they differ for aliased specs (dlx.ts:286).
- Remove the partially-installed prepare dir when the cache install
fails, instead of leaking it across failed runs (pnpm fs.rm on error).
https://claude.ai/code/session_01PPwhryEFfN4iyZkVsjy2Hf
简体中文 | 日本語 | 한국어 | 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:
