3 ms·
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 t
by sotojuan 10y ago
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.
- throwanem 10y agoReally? https://github.com/npm/npm/pulls?q=is%3Apr+is%3Aclosed 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?
- doublerebel 10y agoI'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/12085 https://github.com/npm/npm/issues/8319 https://github.com/npm/npm/issues/8319 https://github.com/npm/couch-login/pull/13 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.
- throwanem 10y agoA 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.