mirror of
https://github.com/pnpm/pnpm.git
synced 2026-03-30 21:11:55 -04:00
35d5318ed7
* fix: resolve relative path params in global add against CWD When running `pnpm -g add .`, the "." was resolved relative to the temporary install directory instead of the user's working directory. This happened because handleGlobalAdd switches opts.dir to a fresh temp directory before the dependency selectors are resolved. Now relative path params (., ./foo, ../bar, file:./foo, link:../bar) are resolved to absolute paths before the directory is switched. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com> * fix: resolve relative local selectors against opts.dir instead of process.cwd() This fixes `pnpm -C <dir> -g add .` where the relative selector would incorrectly resolve against process.cwd() instead of the user's intended directory. Also adds test coverage for file: and link: prefixed selectors. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com> * fix(config): stop overwriting dir to globalPkgDir for global commands Previously, `pnpmConfig.dir` was set to `globalPkgDir` when `--global` was used. This caused `opts.dir` to point to the global packages directory instead of the user's CWD, breaking `pnpm -g add .` because relative paths resolved against the wrong directory. Now `pnpmConfig.dir` is always set to the user's CWD. Global command handlers already use `opts.globalPkgDir` where they need the global packages directory. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com> * fix: use globalPkgDir in pnpm root -g handler The root command handler was using opts.dir which no longer points to the global packages directory. Use opts.globalPkgDir instead. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com> --------- Co-authored-by: Claude Opus 4.6 <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 env use.
- Works everywhere. Supports Windows, Linux, and macOS.
- Battle-tested. Used in production by teams of all sizes since 2016.
- 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:
