Re:Yarn – A new package manager for JavaScript
by softawre on Tuesday October 11, 2016 @01:53PM
(#12686766)
they have millions of installs and can't break them?
[ Parent
| on HN ]
Re:Yarn – A new package manager for JavaScript
by striking on Tuesday October 11, 2016 @02:01PM
(#12686863)
Well, but remember that time they shipped an SSL cert that broke all updated clients? I'm not sure they move slowly because they don't want to break things, because that would have been a pretty easy bug to catch...
http://blog.npmjs.org/post/78165272245/more-help-with-selfsi...
Re:Yarn – A new package manager for JavaScript
by ssunstruck on Tuesday October 11, 2016 @02:32PM
(#12687211)
That's not really a good counter example. It's more of a mistake on a release...
Re:Yarn – A new package manager for JavaScript
by striking on Tuesday October 11, 2016 @04:05PM
(#12688058)
It's more of a failure to double check that npm runs when you change the SSL cert you bundled with it.
I think it's a great example of moving a little too quickly, honestly. Especially since it bricked plenty of npm installs instead of being "just another bug".
Re:Yarn – A new package manager for JavaScript
by BinaryIdiot on Tuesday October 11, 2016 @04:39PM
(#12688333)
Do they necessarily have to break them to move faster? It's a package installer. Yarn is handling locking / shrinkwrapping different but I would argue shrinkwrap needs to be abandoned and re-done anyway so I'm not seeing the risk. It took them, what, two years just to flatten dependencies and move to npm 3? That was actively breaking Windows usage of node!
I love the service they offer. Not a fan of the tools or pace. Npm comes in the node installer so why do they even have to care about improving?
Just my thoughts.