3 ms·
> Yarn is a perfect example. It came out very recently, relatively speaking. And yet it's clearly the future. Like, the only reason not to use yarn is if you ha
by ashark 9y ago
> Yarn is a perfect example. It came out very recently, relatively speaking. And yet it's clearly the future. Like, the only reason not to use yarn is if you have a legacy app that explodes for some reason if you try to type "yarn" instead of "npm install". But the common case is that you do "git clone foo && cd foo && yarn" and everything works perfectly.
Last I checked its issue tracker was a pile of "hey, you, uh, didn't implement this npm feature at all, so things break" and "you're missing yet another obvious sanity check here, so things break". No wonder it's faster. The last thing I need in my JS stack is another thing that can fail under ordinary use, for marginal benefit.
- pluma 9y agoIf you think npm is less buggy, you haven't been paying attention after the npm 5 release. Or when npm had an obvious race condition that resulted in publish breaking at random for years. Let's not pretend npm is slowed down by being well-crafted and reliable.
- ashark 9y agoI've not personally encountered an NPM bug ever, as far as I can recall, and hit a couple inside a week of using Yarn. So I'm gonna keep not using it for the time being, since there's no real difference aside from not having to spend time ruling out my package manager as a source of broken builds.
- pluma 9y agoI've run into several NPM bugs (including publishing broken packages because of that race condition bug several times) and have yet to run into any problems with Yarn. You do you, though.