bf77ed25ea
* ci: run required checks on merge_group so the merge queue works The merge queue dispatches a merge_group event against a temporary gh-readonly-queue/main ref, but neither TS CI (ci.yml) nor Rust CI (pacquet-ci.yml) listened for it. Their required status checks therefore never ran in the queue, so every queued PR waited forever on the missing contexts (e.g. Rust CI / Success never starting). Add merge_group to both workflows' triggers and force the change detection true for that event. Forcing matters because TS CI / Compile & Lint is itself a required context: a skipped job never reports its context, which would keep the queue waiting, so it has to actually run. It also makes the queue test the fully merged result, which is the point of a merge queue. The Rust deny job's nested path filter, which has no push/PR base to diff against in the queue, runs unconditionally on merge_group instead. * ci: gate compile-and-lint and build-pnpr on merge_group explicitly The merge queue tests the merged commit, so the gating jobs must run on merge_group. build-pnpr (added by the Windows-sharding work) carries the same event guard as compile-and-lint and feeds test-smoke/test/test-windows, so it needs the merge_group clause too — otherwise the queue would skip the whole test suite.
简体中文 | 日本語 | 한국어 | 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.