pnpm

    pnpm/pnpm

    Fast, disk space efficient package manager

    backend
    dependency-manager
    install
    javascript
    modules
    node
    nodejs
    npm
    package-manager
    TypeScript
    MIT
    34.1K stars
    1.3K forks
    34.1K watching
    Updated 2/27/2026
    View on GitHub
    Backblaze Advertisement

    Loading star history...

    Health Score

    25.55

    Weekly Growth

    +7

    +0.0% this week

    Contributors

    1

    Total contributors

    Open Issues

    2.1K

    Generated Insights

    About pnpm

    简体中文 | 日本語 | 한국어 | Italiano | Português Brasileiro

    pnpm

    Fast, disk space efficient package manager:

    • Fast. Up to 2x faster than the alternatives (see benchmark).
    • Efficient. Files inside node_modules are 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.

    npm version OpenCollective OpenCollective X Follow Stand With Ukraine

    Platinum Sponsors

    Bit

    Gold Sponsors

    Discord CodeRabbit Workleap
    Stackblitz Vite

    Silver Sponsors

    u|screen Leniolabs_ Depot
    devowl.io Cerbos Vite
    OOMOL Studio

    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:

    1. 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 update will only add 1 new file to the storage.
    2. 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

    Discover Repositories

    Search across tracked repositories by name or description