News for hackers. Stuff that matters.
Re:How we run NPM packages in the browser by ianjsikes on Saturday October 07, 2017 @11:07PM (#15426798)
What's so funny? Yarn uses the npm package registry, so it is a package manager for npm.
Re:How we run NPM packages in the browser by owebmaster on Sunday October 08, 2017 @01:27AM (#15427082)
A package manager for a package manager is indeed a funny thing that shows the overengineering of the JS ecosystem. Facebook could improve npm but they would not profit too much from it so yarn.
Re:How we run NPM packages in the browser by allover on Sunday October 08, 2017 @07:09AM (#15427778)
> 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.

Re:How we run NPM packages in the browser by owebmaster on Sunday October 08, 2017 @07:16PM (#15430569)
> 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).

Re:How we run NPM packages in the browser by allover on Monday October 09, 2017 @01:10PM (#15435600)
> 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.

Re:How we run NPM packages in the browser by favadi on Sunday October 08, 2017 @02:18AM (#15427179)
Npm is both a package management and a package registry.
Re:How we run NPM packages in the browser by owebmaster on Sunday October 08, 2017 @07:17PM (#15430573)
Exactly! But mainly, a package manager. If you create a project that tries to replace it and at the same time needs it to exist, I guess funny is a minimum you can say about.
Re:How we run NPM packages in the browser by allover on Monday October 09, 2017 @01:12PM (#15435610)
It's not funny at all. It's totally logical that you'd have competing clients.