Zoltan Kochan
9720df211a
The TypeScript CLI accepts `--stream`, `--aggregate-output`, `--use-stderr`, `--reporter-hide-prefix`, `--ignore-workspace`, and `--workspace-packages`; pacquet rejected all six. Section 2 of pnpm/pnpm#14101. `--stream` is the substantial one. A recursive `run` inherited the terminal for every project, so pacquet had no way to attribute a line to the project that wrote it, and `--parallel` — which expands to `--stream` in pnpm's `run` shorthand table — produced unreadable interleaved output. `RunScript` grows a `ScriptOutput`: `Inherit` keeps the old path, `Streamed` pipes the child and republishes each line as a `pnpm:lifecycle` event through the new `StreamedScript`, which also absorbs the line pumps `run_lifecycle_hook` already had. The reporter gains `streamLifecycleOutput`, so the lifecycle stream renders append-only while the rest of the frame still redraws in place — the same split pnpm's reporter makes. `--aggregate-output` buffers a script's events until it exits and then renders the run as one block, formatting at flush time so the prefix color wheel advances in print order. `--reporter-hide-prefix` drops the prefix from the script's own output lines only, leaving the `$ <script>` echo and the `Done` / `Failed` line labelled. It is a `run` / `exec` option, so it is scope-validated and hidden like the other command-scoped globals; a recursive `exec` reads its explicit `false` as the signal to start prefixing, matching pnpm's `reporterHidePrefix === false` gate. `--ignore-workspace` stops the workspace search in `Config::current`, so `pnpm-workspace.yaml` contributes neither settings nor sibling projects and a blocked dependency build is not scaffolded into its `allowBuilds`. `--workspace-packages` is resolved into `Config::workspace_package_patterns` alongside the manifest's own `packages`, which `discover_workspace_projects` now takes from the config rather than re-reading the manifest at every call site. The five boolean settings also become readable from `pnpm-workspace.yaml`, the global `config.yaml`, and `PNPM_CONFIG_*`. This is pacquet-only: the TypeScript CLI already has all six.
简体中文 | 日本語 | 한국어 | 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.