Join GitHub today
GitHub is home to over 31 million developers working together to host and review code, manage projects, and build software together.Sign up
Use yarn instead of npm #53
It can be faster in some cases, but I don't have benchmarks on hand. The main reason for me is that the package resolution algos are slightly different.
I ran into an issue where the latest npm (6.9.0) was not able to resolve my package that I had installed via github with
I was able to workaround it by downgrading to npm 5.2.0 after following this thread
However this could have been avoided if I had the ability to use yarn or better yet if zero detected that I was using
I'm in a bit of a crunch mode at the moment but I'll probably try to circle back to this exploration in a few weeks.
I really like that npm is the main option for most developers. I wouldn't go to yarn if it was to leave npm completely.