d1da02e38d
Add the `publish` command to pacquet — the Rust port's first `releasing` command — bringing it to parity with `pnpm publish`. It implements single-package and tarball publish (pack -> build the npm publish document -> PUT /:pkg, with private / unscoped-restricted validation and semver cleaning); recursive / --filter workspace publish (dependency-ordered, skipping private / unnamed / already-published packages via concurrent registry probes, with --report-summary and --json, and the filter-without--r recursive promotion); OIDC trusted publishing with keyless sigstore SLSA provenance (Fulcio + Rekor); OTP / web-auth; git pre-publish checks (git-checks config and --no-git-checks); publish-lifecycle scripts; and the --access / --tag / --dry-run / --force / --ignore-scripts / --skip-manifest-obfuscation / --publish-branch flags. --batch is accepted for surface parity but errors, as it is not yet ported. The external-service side effects — OIDC HTTP, the clock, CI-provider detection, subprocess spawns, and the sigstore signing step — are each behind a self-less capability trait on a Host provider, threaded as a Sys generic, so the flows are unit-testable offline with fakes. The web-auth OTP fakes live in a dedicated pacquet-network-web-auth-testing crate and are expanded per test by a web_auth_fake!() macro. The `pacquet publish` binary is additionally covered by integration tests that drive it against a mockito registry. Related to pnpm/pnpm#11633. A live end-to-end publish harness (a pnpr instance implementing OIDC / OTP / web-auth / provenance) is tracked by pnpm/pnpm#12738, and real sigstore signing by pnpm/pnpm#12739. --------- Co-authored-by: Claude <noreply@anthropic.com> 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.