跳到主要内容

Benchmarks of JavaScript Package Managers

Last benchmarked at: Sep 29, 2024, 3:14 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).

Here's a quick explanation of how these tests could apply to the real world:

  • clean install: How long it takes to run a totally fresh install: no lockfile present, no packages in the cache, no node_modules folder.
  • with cache, with lockfile, with node_modules: After the first install is done, the install command is run again.
  • with cache, with lockfile: When a repo is fetched by a developer and installation is first run.
  • with cache: Same as the one above, but the package manager doesn't have a lockfile to work from.
  • with lockfile: When an installation runs on a CI server.
  • with cache, with node_modules: The lockfile is deleted and the install command is run again.
  • with node_modules, with lockfile: The package cache is deleted and the install command is run again.
  • with node_modules: The package cache and the lockfile is deleted and the install command is run again.
  • update: Updating your dependencies by changing the version in the package.json and running the install command again.

Lots of Files

The app's package.json here

actioncachelockfilenode_modulesnpmpnpmYarnYarn PnP
install33.1s8.6s7.3s3.5s
install1.5s1s5.2sn/a
install7.8s2.6s5.4s1.3s
install12.8s6s7.2s2.9s
install11.8s5.3s5.5s1.3s
install1.7s2.4s7.1sn/a
install1.4s1s5.2sn/a
install1.7s5.4s7sn/a
updaten/an/an/a6.5s3.7s5.8s3s
Graph of the alotta-files results