A
fd33859bcd
Replace the ERR_PNPM_NOT_IMPLEMENTED stub with the npm-style form: `pnpm version <major|minor|patch|premajor|preminor|prepatch|prerelease>` and `pnpm version <exact-version>` (a leading `v` is accepted and stripped, like semver.valid), also recursively with `-r`/`--filter`. The bare `pnpm version -r` change-intents release flow is untouched. The bump follows node-semver's inc() with its default identifier base of 0 — bumping major/minor/patch from a matching prerelease finalizes it, the pre* types start a `.0` prerelease honoring `--preid`, and `prerelease` increments the right-most numeric identifier. Options mirror the TypeScript CLI: `--allow-same-version`, `--message` with `%s` substitution, `--no-git-tag-version`, `--no-commit-hooks`, `--sign-git-tag`, `--tag-version-prefix` (default "v"), and `--json`. The single-package form records the bump as a commit plus an annotated (or GPG-signed) tag through the same RunCommand capability the publish git checks use; recursive runs skip the commit and tag since there is no single version to tag with. The preversion/version/postversion scripts run through pacquet-executor's run_lifecycle_hook — the same port of the upstream exec.lifecycle package the TypeScript handler calls — re-reading the manifest between stages so each hook sees the right version. Error codes match pnpm: ERR_PNPM_INVALID_VERSION_BUMP, ERR_PNPM_INVALID_VERSION, ERR_PNPM_VERSION_NOT_CHANGED, ERR_PNPM_NO_PACKAGES_TO_VERSION, ERR_PNPM_UNCLEAN_WORKING_TREE. The TypeScript CLI already ships this form, so only the pacquet side changes; no TypeScript change is needed. Covers the remaining `version` gap under the Stage 3 command surface in pnpm/pnpm#11633. Tests: a unit table driving inc() through the node-semver cases, plus integration tests against the built binary porting the upstream scenarios from releasing/commands/test/version/index.test.ts and pnpm/test/version.ts — bumps, preid, JSON output, explicit versions, same-version handling, lifecycle-hook ordering, the git commit/tag matrix, and recursive selection with and without --filter.
简体中文 | 日本語 | 한국어 | 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.