e3f2be02f0
GitHub's merge queue runs each entry on a temporary `gh-readonly-queue/**` branch, whose creation also fires a `push` event. For `ci.yml` (`on: [push, pull_request, merge_group]`) that produced two TS CI runs for the identical commit: one `push`, one `merge_group`. Both reach the reusable `test.yml`, whose concurrency group keys on `github.ref` with `cancel-in-progress: true`. Since the two runs share `github.ref`, their per-(platform, node, chunk) test jobs land in the same group and cancel each other. The Windows shards are gated only on compile-and-lint + build-pnpr, so both runs' Windows jobs start near-simultaneously and reliably collide. The `merge_group` run — the only one the queue's required `TS CI / Success` check reads — lost the race, so its cancelled test jobs failed `Success` and ejected the PR for "failed status checks". Restrict the `push` trigger to ignore `gh-readonly-queue/**` so only the `merge_group` run executes for queued commits. `pacquet-ci.yml` already scopes push to `main` and was unaffected. Apply the same `branches-ignore` to `audit.yml` to drop its redundant push run on those branches.
简体中文 | 日本語 | 한국어 | 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.