June 28, 2017

pnpm 1.0 released

Zoltan Kochan released pnpm 1.0 on June 28, 2017 — an npmNode Package Manager — the default registry and CLI for installing JavaScript and TypeScript libraries.-compatible package manager using a content-addressed store and symlinks.

What it was for

Pnpmpnpm installs each package version once on disk and hard-links it into `node_modules` — slashing duplicate copies across projects. Strict dependency resolution catches phantom imports that npmNode Package Manager — the default registry and CLI for installing JavaScript and TypeScript libraries. and YarnA JavaScript package manager — alternative to npm with lockfiles and workspace monorepo support. allowed. Monorepo workspaces, filtering, and fast CI installs made it the choice for teams hitting `node_modules` bloat after YarnA JavaScript package manager — alternative to npm with lockfiles and workspace monorepo support.'s lockfile revolution.

Why it's here

pnpm proved symlinked node_modules could be strict, fast, and compatible with the npmNode Package Manager — the default registry and CLI for installing JavaScript and TypeScript libraries. ecosystem.

Why it mattered

It forced a rethink of disk usage and dependency isolation in JavaScript package management.

What it solved

Duplicate packages across projects wasted disk and hid missing dependency declarations.

Media

  • Pnpm
    ImagePnpm

    Zoltan Kochan and other contributors, MIT, via Wikimedia Commons

Related