LEleipert·Jul 9, 2017
The killer feature for us was a more maintainable lock file. Back when we switched, it was way more readable than the npm-shrinkwrap.json and it is easier to fix merge conflicts in the yarn.lock.
And if you are wondering: Why a lockfile? It has also been a game changer, everyone in my team has the same dependencies installs, dependencies do not suddenly break. (Anecdote: Before the switch some dependency of an dependency of an dependency overwrote some Array function, and broke our whole product. I was on vacation and had to fix this remotely, because it was kind of hard to debug).
The only obstacles we ran into:
1) private registries did not work, but this has been fixed
2) yarn upgrade command behavior is sometimes funny, but this is going to be fixed soon:
- https://github.com/yarnpkg/yarn/issues/3603
- https://github.com/yarnpkg/rfcs/