News for hackers. Stuff that matters.

A comment on Everything You Wanted to Know About Yarn Package Manager. Parent comment

Re:Everything You Wanted to Know About Yarn Package Manager by sotojuan on Tuesday October 18, 2016 @11:55AM (#12735673)
I don't get why people say this. You're acting like the npm team is desperate for contributions and fixes and the Yarn people are like "No! We'll make our OWN tool!".

It's the literal opposite. npm hasn't been open to contributions or fixes for years.

[ Parent | on HN ]
Re:Everything You Wanted to Know About Yarn Package Manager by throwanem on Tuesday October 18, 2016 @12:27PM (#12736055)
Really? https://github.com/npm/npm/pulls?q=is%3Apr+is%3Aclosed would seem to suggest otherwise. Should I be looking elsewhere? Is there something I'm not seeing here?
[ Parent | on HN ]
Re:Everything You Wanted to Know About Yarn Package Manager by doublerebel on Tuesday October 18, 2016 @05:45PM (#12739014)
I've contributed multiple issues and PRs which have been completely ignored. It seems from the outside that their focus on monetizing causes their API to be purposefully opaque and subject to change. It's been disappointing and certainly turns me off from ever purchasing private repo hosting from npm itself.

For reference:

https://github.com/npm/npm/issues/12085

https://github.com/npm/npm/issues/8319

https://github.com/npm/couch-login/pull/13

I have a deep understanding of how it works now, and therefore more to contribute, but what's the point? I just keep running my own npm(s) instead and contribute to packages that appreciate it.

[ Parent | on HN ]
Re:Everything You Wanted to Know About Yarn Package Manager by throwanem on Tuesday October 18, 2016 @06:43PM (#12739381)
A strong statement, to be sure, for which one would hope to see equally strong evidence. But two out of those three issues have unfulfilled requests for followup. I'm not sure quite what you mean them to show.
[ Parent | on HN ]