[allover]

> A package manager for a package manager

It's not, it's a package manager for a package registry.

> that shows the overengineering of the JS ecosystem

Nope.

> Facebook could improve npm but they would not profit too much from it so yarn

Explain? 1. I don't see how Facebook profits from Yarn. 2. The npm cli is hard to contribute to, the npm team themselves admit that, so it's fairly obvious to me why it made more sense to build a new client at the time, given the design goals of Yarn.

[owebmaster]

> It's not, it's a package manager for a package registry.

npm is not a package registry. Is a package manager with a package registry.

> 2. The npm cli is hard to contribute to, the npm team themselves admit that, so it's fairly obvious to me why it made more sense to build a new client at the time, given the design goals of Yarn.

Are you following the painful mess Facebook has been doing lately with their own projects? Broken react, broken react native, broken metro-bundler. I'm sure yarn doesn't help with it. And if you are not sure how facebook profits from yarn and its open source ecosystem, I think you don't get what open source means (and it is not free software).

[allover]

> It's not, it's a package manager for a package registry.

>> npm is not a package registry. Is a package manager with a package registry.

Not sure what point you're trying to make. Yarn is a package manager for the npm package registry.

> Are you following the painful mess Facebook has been doing lately with their own projects? Broken react, broken react native, broken metro-bundler

I do React for a living. It's not broken. I don't do React Native, but not aware it's broken. I don't care about metro-bundler.

> I'm sure yarn doesn't help with it.

Yarn did help matters for a long time, it's a great package manager. Now that npm 5 is mature, I don't use Yarn anymore, but I'm glad it existed to stir up competition.

> And if you are not sure how facebook profits from yarn and its open source ecosystem

We're talking about yarn specifically. The context was choosing to build yarn vs contributing to npm.