bteaandZoltan Kochan
7e7b899daf
`pnpm deploy`, `pnpm rebuild`, `pnpm rb`, and `pnpm setup` now run a `package.json` script of the same name, as documented. `pnpm pm <name>` still forces the built-in command. The resolver that `clean` / `purge` already used moves to `cli_args::script_override` and serves all six commands. `rb` becomes a clap variant of its own rather than a `visible_alias` of `rebuild`, because pnpm looks the overriding script up under the name that was typed, as pnpm 11 does with `argv.remain[0]`. A redirected command behaves as `pnpm run <script>`, so the install-family `Done in ...` footer of the typed command no longer follows the script output. `script_override::resolve` records the redirect on the run context and `CliArgs::run` reads it. `clean` dispatches its redirect through `dispatch_script::run` like the other commands, which gives it the pnpmfile `updateConfig` pass and the recursive handling it was skipping. Separately, `dispatch_install::ci` dispatched its clean step through the overridable path, so a project with a `clean` script ran that script instead of emptying `node_modules` and the frozen install proceeded over a stale tree. `ci` is not an overridable command in pnpm 11 either, where `cleanInstall` calls the clean handler directly. It now calls the built-in unconditionally. That bug predates this branch and carries its own changeset. --------- 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.
- 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.