Benchmarks of JavaScript Package Managers

Last benchmarked at: Jun 2, 2026, 9:03 AM (daily updated).

This benchmark compares the performance of npm, pnpm, Yarn Classic, and Yarn PnP (check Yarn's benchmarks for any other Yarn modes that are not included here).

Each row's label lists which of cache, lockfile, and node_modules are warm/present before install runs. Quick mapping to the real world (ordered from slowest to fastest scenario):

• clean: a brand-new clone — nothing cached, no lockfile, no node_modules.
• cache: a developer reinstalling without a lockfile.
• lockfile: a CI server doing its first install.
• cache+lockfile: a developer reinstalling a known project.
• cache+node_modules: the lockfile is deleted and install is run again.
• node_modules: the cache and lockfile are deleted and install is run again.
• lockfile+node_modules: the cache is deleted and install is run again.
• cache+lockfile+node_modules: re-running install when nothing has changed.
• update: dependency versions are bumped in package.json and install is run again.

Lots of Files​

The app's package.json here

pnpm vs pnpm 🦀​

pnpm v12 will use a new installation engine for fetching and linking written in Rust. See pacquet.