Popularity
8.3
Growing
Activity
9.8
Growing
14,809
102
409

Description

pnpm uses hard links and symlinks to save one version of a module only ever once on a disk. When using npm or Yarn for example, if you have 100 projects using the same version of lodash, you will have 100 copies of lodash on disk. With pnpm, lodash will be saved in a single place on the disk and a hard link will put it into the node_modules where it should be installed.

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: Why should we use pnpm? https://www.kochan.io/nodejs/why-should-we-use-pnpm.html

Monthly Downloads: 0
Programming language: TypeScript
License: MIT License
Latest version: v5.5.12

pnpm alternatives and similar libraries

Based on the "Package Managers" category.
Alternatively, view pnpm alternatives based on common mentions on social networks and blogs.

  • yarn

    9.6 3.0 L3 pnpm VS yarn
    The 1.x line is frozen - features and bugfixes now happen on https://github.com/yarnpkg/berry

  • npm

    9.2 2.1 L4 pnpm VS npm
    npm is the package manager for javascript.

    • Scout APM allows you to find and fix performance issues with no hassle. Now with error monitoring and external services monitoring, Scout is a developer's best friend when it comes to application development.
    Promo

  • Bower

    8.8 4.7 L4 pnpm VS Bower
    A package manager for the web

  • component

    6.1 0.0 L5 pnpm VS component
    Client package management for building better web applications.

  • jspm

    5.5 2.4 L2 pnpm VS jspm
    Frictionless browser package management.

  • Duo

    5.3 0.0 L4 pnpm VS Duo
    Next-generation package manager that blends the best ideas from Component, Browserify and Go to make organizing and writing front-end code quick and painless.

  • Ender

    3.9 0.0 L5 pnpm VS Ender
    the no-library library: open module JavaScript framework

  • jam

    3.8 0.0 L5 pnpm VS jam
    A package manager using a browser-focused and RequireJS compatible repository.

  • volo

    3.7 0.0 L2 pnpm VS volo
    Create front end projects from templates, add dependencies, and automate the resulting projects

  • spm

    3.6 0.0 pnpm VS spm
    Brand new static package manager.

  • Refraction

    1.4 0.0 L5 pnpm VS Refraction
    A guard that represents a central point of control in your application

Do you think we are missing an alternative of pnpm or a related project?

Add another 'Package Managers' Library
Deliver Cleaner and Safer Code - Right in Your IDE of Choice!
sponsored www.sonarlint.org

Popular Comparisons

OPS - Build and Run Open Source Unikernels
sponsored github.com/nanovms

README

中文 | 日本語 | Italiano | Русский | Français

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.

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 Join the chat at Discord OpenCollective OpenCollective Twitter Follow

Sponsors

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 or Yarn, 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:

Backers

Thank you to all our backers! Become a backer

Contributors

This project exists thanks to all the people who contribute. [Contribute](../../blob/main/CONTRIBUTING.md).

License

MIT


*Note that all licence references and agreements mentioned in the pnpm README section above are relevant to that project's source code only.