751af41ccf
* fix(path-extender-posix): keep lines between duplicate pnpm sections `@pnpm/os.env.path-extender-posix` replaced the pnpm section with a greedy regex, so a shell config holding two `# pnpm` ... `# pnpm end` blocks lost everything between the first opening marker and the last closing one. pnpm/pnpm#15321 already fixed this for `pnpm setup`, but it did so in a copy of the package inside `@pnpm/engine.pm.commands`, because the package still lived in pnpm/components. Now that the package is in this repository, move the fixed code and its tests back into it and let `pnpm setup` use the package again. The copy is deleted. The regression test for the published API is adapted from pnpm/components#29 by Zelys, which proposed a non-greedy regex for the same bug. Closes https://github.com/pnpm/pnpm/issues/12282 Co-authored-by: Zelys <zelys@dfkhelper.com> Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * fix(path-extender-posix): prefer the block that sets proxyVarName The duplicate-section selection looked for `<SECTION>_HOME`, which misses the generated block when a caller's `proxyVarName` differs from its section name. Pass `proxyVarName` through to `findSection`. Also declare the section helpers after `updateShellConfig`, document the `null` result, and reword the changeset. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> --------- Co-authored-by: Zelys <zelys@dfkhelper.com> Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
简体中文 | 日本語 | 한국어 | 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.