跳至主要內容

Benchmarks of JavaScript Package Managers

Last benchmarked at: Feb 18, 2024, 2:44 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
install35.6s9s7.4s3.7s
install1.5s1.1s4.9sn/a
install7.2s2.7s5.4s1.4s
install12.8s6.2s7.7s3.1s
install12.3s5.4s5.4s1.4s
install1.7s2.4s7.1sn/a
install1.5s1.1s4.9sn/a
install1.7s5.4s7sn/a
updaten/an/an/a8.1s4s5.7s3.1s
Graph of the alotta-files results