Trevor Burnham
620d3f24fc
pnpm/pnpm#14458 fixed `link`, `outdated` and `import`, the three that failed outright. The rest of the commands in pnpm/pnpm#14444's survey still skip the `updateConfig` hook: `fetch` fails with `ERR_PNPM_LOCKFILE_CONFIG_MISMATCH` once a hook's settings reach the lockfile, and `why`, `list`, `ll`, `licenses`, `audit`, `patch`, `sbom`, `peers` and `runtime` silently discard whatever the hook changed. The commands split by where their config comes from. `list`, `licenses` and `peers` hold a `Config` directly, so they apply the pass the script commands already use. The rest build a `State`, whose `State::init` resolves the manifest against the config it is handed and then owns it — the hooks have to run before that, but `RunCtx::state` is a sync closure and the pass is async. `RunCtx::prepared_state` is its awaitable counterpart: it loads the config, applies the hooks, and only then initializes the state. `outdated`, `import` and `link` move onto the helper too, so the three copies pnpm/pnpm#14458 inlined become one. `patch-commit`, `patch-remove` and `approve-builds` keep the sync closure. They build state more than once per invocation, so routing them through the async pass would run the pnpmfile once per build instead of once per invocation; they reach the hooks through the install they end in. Closes pnpm/pnpm#14444.
简体中文 | 日本語 | 한국어 | 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.