Hacker News Reader

Is there any reason to use Yarn now that NPM has comparable speed and lockfiles?

Anecdotally, yarn is significantly faster. Makes a difference if you have lots of dependencies.

I used npm a lot and had sporatic unexplainable errors. I haven't used npm 5 to say if it's been fixed, but that turned me off.

I've had this issue too with npm on my build server - sometimes things just fail, maybe it's flaky network, maybe it's some package update that didn't quite go as planned, but yarn seems to solve it and works a lot faster to boot, so I'll be sticking with it for now.

npm5 and 5.1 has improved performance significantly so that it's comparable with yarn.

We switched to yarn in the past and switch back to NPM a couple of weeks back, after npm 5 delivered usable performance.

A problem with yarn was, that it has trouble upgrading all dependencies: https://github.com/yarnpkg/yarn/issues/3492

Reply on news.ycombinator.com