* docs(contributing): document Rust toolchain and git-hook tooling Rust is now the primary language in this repository, but the root CONTRIBUTING.md only covered the TypeScript setup. Add a "Rust toolchain and git hooks" section under "Setting Up the Environment" that covers rustup and the pinned toolchain, just, the just init tools, and the dylint tools. Two things that are easy to get wrong and cost real debugging time: - cargo-dylint and dylint-link must be installed from source, not with cargo binstall. The prebuilt binaries reference the dylint_driver crate at the path where they were built, so building the per-toolchain driver fails locally with an error pointing at a nonexistent .../dylint/driver directory. - ~/.cargo/bin must be on PATH (ahead of any system Rust in /usr/bin), because the pre-push hook locates its tools through PATH and silently skips a Rust check when the tool is missing rather than failing, so a push that looks clean locally can still fail format, doc, or dylint in CI. Point pacquet/CONTRIBUTING.md at the new root section instead of repeating the tool list, and correct its cargo binstall advice for the dylint tools. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com> * docs: correct dylint install hint in justfile and pre-push hook The `just dylint` recipe comment and the pre-push hook's skip message both told contributors to install cargo-dylint via `cargo binstall`, which produces a prebuilt binary that fails to build the per-toolchain driver locally. Point both at `cargo install` from source, matching the CONTRIBUTING.md guidance. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com> --------- Co-authored-by: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
jsr: and named-registry package names (empty scope/name, path separators) (#12677)
简体中文 | 日本語 | 한국어 | 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.