Skip to main content

Benchmarks of JavaScript Package Managers

Last benchmarked at: Dec 3, 2021, 2:50 AM (daily updated).

This benchmark compares the performance of npm, pnpm, and Yarn (both regular and PnP variant).

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
install1m 12.2s14.8s22.1s27.5s
install1.6s1.2s2.6sn/a
install9.5s3.6s8.6s1.9s
install14.2s8.7s14.2s7.4s
install25.4s13.5s15.3s21.1s
install2.1s1.7s8.3sn/a
install1.6s1.2s9.4sn/a
install2.1s5.1s15sn/a
updaten/an/an/a1.6s11s18.7s32.4s

Graph of the alotta-files results