Javacripter at Bugsnag, also an occasional pixel artist
This post was originally published on the Bugsnag blog. Bugsnag’s real-time error monitoring platform is the most practical way to improve software quality for your users. With visibility into production errors alongside diagnostic data for reproducing and fixing, developers can improve customer experiences and code quality.
The initial gut reaction may be to get wound up about the notion of forking essential tooling. However, yarn works in a way that is compatible with existing infrastructure. It still uses the existing npm registry and its CLI is mostly identical to that of
The Bugsnag frontend team was on pins and needles to give it a spin, primarily because we have frequently gotten tangled up by dependencies changing between different developers' machines. We often have to delete our node_modules folder and re-install everything to solve mysterious problems. We've tried npm's shrinkwrap feature before, but, like Facebook, there were issues with it getting out of date so we've been itching for an alternative solution for some time.
Yarn solves this problem by using an automatically updated "lockfile" to tie down the dependencies to a specific version. After this file is committed to source control, we should never have to worry about inconsistent dependencies between machines or variations over time.
The migration process was extremely simple. Just run the
yarn command and commit the resulting
yarn.lock file. Then grep all our docker and deploy scripts for references to
npm and replace them with the yarn equivalents.
Some initial rough benchmarks look very promising. Just so you know the wool hasn't been pulled over your eyes, here are the raw numbers.
|command||time (in seconds)|
Yarn will cache dependencies so subsequent installs can be done without re-downloading. This even works without an internet connection.
Even without caching, Yarn is faster due to parallelization.
I'm especially excited about the impact it will have on the CI server where we start with a fresh node_modules folder for every build.
The API is mostly the same with a few notable exceptions. With NPM the default
npm install <some-package> command would not add the dependency to
package.json, where as
yarn add <package-name> will. I think this is preferable as the default behavior since the alternative makes it too easy to forget to commit a dependency change.
Yarn also adds several bonus features. The
yarn why command, which will show you which of your dependencies is causing a package to be downloaded.
These are only some initial impressions of yarn. There are also many features that I didn't get to cover. Check out the official site to learn more, including the security enhancements, performance features, and flat mode.