3 ms·
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 buil
by steveklabnik 10y ago
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 https://github.com/yarnpkg/rfcs !
- jlongster 10y agoHuh, interesting! I thought this was going to just be a client. I wonder if it resolved to npm's servers or something.
- steveklabnik 10y agoA curl -I shows CloudFlare, at least. npm's does not. So it's at _least_ doing some sort of cache...
- thejameskyle 10y agoOh hi Steve! https://registry.yarnpkg.com 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.
- steveklabnik 10y agoMakes total sense, thanks for elaborating! I don't do very much node dev, but when I do, it'll be yarn from now on.
- ag_dubs 10y agohi! 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/ https://npmjs.cf/ for a long time.
- wycats 10y agoAt 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.
- k__ 10y agoIt'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?
- ag_dubs 10y agoied didn't work on windows because of the linking strategy. many people who need to use npm use windows.
- blubbi2 10y agoThat'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.)
- deleted 10y ago[deleted]