Table of Contents
Most tools don’t usually generate this much adoption and conversation right off the bat. Here are three factors that led to all the hype.
1. The Technology: Yarn Addresses Serious npm Shortcomings
Since Yarn dropped, there’s been plenty of articles comparing it to npm. We’ve condensed the technicalities down to a few key differences.
Core functional differences:
- Speed: Instead of re-downloading each and every package (and its dependencies), Yarn caches the packages on each install. That makes Yarn a whole lot faster than npm. When we installed Yarn, we reduced build times from 7 minutes to 2.5 minutes.
- Flat mode: Yarn has a flat dependency structure, whereas npm has a nested structure.
- Offline mode: If you’ve already installed a package, you can install it again without an internet connection.
- Emojis: Who doesn’t love emojis? Yarn allows them, npm doesn’t.
- A yarn.clean function that removes dependency bloat (scotch)
As tomdale put it on Hacker News, Yarn is “a huge leap forward for the JavaScipt–probably more than many people will realize right away.”
2. The Names: Yarn was Built and Promoted by Big-Name Developers
The developers working on Yarn also generated some buzz. The developer team included…
- Tom Occhino (instrumental in React),
- Chris Pojer (big contributor to Jest),
- Sebastian McKenzie (the author of Babel),
- Yehuda Katz (creator of Bundler and key contributor to Ember.js)
Noted open source evangelists Addy Osmani and Paul Irish also helped spread the word. With a team like this, it’s no wonder that the Yarn launch had people talking.
3. The Accessibility: Open Source Invites Adoption and Engagement
Yarn made a point to embrace open source collaboration from day one. Not only was it built by developers from different organizations, but they explicitly asked developers to contribute in their initial announcement. So far, it’s worked! The project already has 34 pull requests and 122 contributors on GitHub.
Another factor? Yarn was incredibly easy to install. All we had to do was run one line of code. Seriously. This was it.
Having a low barrier to entry meant that it was even easier for people to try it out and start contributing code right away.
What do you think? Have you tried Yarn yet? Let us know in the comments below!