News for hackers. Stuff that matters.
Re:Yarn – A new package manager for JavaScript by steveklabnik on Tuesday October 11, 2016 @11:12AM (#12685110)
It looks like this addresses the biggest issues people have with npm's CLI, and it's coming from such huge names: Facebook, Google, and Tilde. Reproducible builds are a _huge_ issue, and this gives you that. Looks great!

One interesting little tidbit I found from diving into the source:

  https://github.com/yarnpkg/yarn/blob/master/src/constants.js#L15

  https://github.com/yarnpkg/yarn/blob/master/src/registries/yarn-registry.js
It's not mentioned in the post, but looks like they're running their own registry as well...

Oh! And open governance: https://github.com/yarnpkg/rfcs !

Re:Yarn – A new package manager for JavaScript by thejameskyle on Tuesday October 11, 2016 @11:16AM (#12685146)
Oh hi Steve! https://registry.yarnpkg.com is just a proxy to the normal npm registry provided by Cloudflare so we can add additional caching and work on network performance (lots of stuff we could layer on top). It should hopefully help those in China as well which would be awesome. But everything you do still lives on the normal npm registry.
Re:Yarn – A new package manager for JavaScript by steveklabnik on Tuesday October 11, 2016 @11:20AM (#12685183)
Makes total sense, thanks for elaborating! I don't do very much node dev, but when I do, it'll be yarn from now on.
Re:Yarn – A new package manager for JavaScript by ag_dubs on Tuesday October 11, 2016 @11:21AM (#12685203)
hi! they are running a mirror of the npm registry which contains all the package data but none of the permissions/user mgmt. this means that they are still dependent on npm infrastructure.

npm, Inc strongly encourages people to build and use mirrors. for example, cloudflare (where the mirror lives, and where seb used to work) has been running https://npmjs.cf/ for a long time.

Re:Yarn – A new package manager for JavaScript by wycats on Tuesday October 11, 2016 @11:28AM (#12685273)
At least speaking for myself, the npm package ecosystem is critical and I wouldn't want to do anything to undermine the integrity of the npm registry.
Re:Yarn – A new package manager for JavaScript by k__ on Tuesday October 11, 2016 @11:26AM (#12685253)
It's not the first one addressing these problems.

Nix and ied (which borrowed from Nix) got these problems pretty much solved.

I don't understand what spoke against these approaches?

I mean okay, nix has its own language, which is probably a turnoff for JS devs, but ied?

Re:Yarn – A new package manager for JavaScript by ag_dubs on Tuesday October 11, 2016 @11:43AM (#12685426)
ied didn't work on windows because of the linking strategy. many people who need to use npm use windows.
Re:Yarn – A new package manager for JavaScript by blubbi2 on Tuesday October 11, 2016 @11:17PM (#12690220)
That's not 100 % accurate. Arguably symlinks are kinda weird under Windows, but that doesn't mean symlinking node_modules doesn't work (you just need admin privileges).

(Disclaimer: I'm the author of ied.)

Re:Yarn – A new package manager for JavaScript by jlongster on Tuesday October 11, 2016 @11:14AM (#12685119)
Huh, interesting! I thought this was going to just be a client. I wonder if it resolved to npm's servers or something.
Re:Yarn – A new package manager for JavaScript by steveklabnik on Tuesday October 11, 2016 @11:18AM (#12685170)
A curl -I shows CloudFlare, at least. npm's does not. So it's at _least_ doing some sort of cache...