I think the write-up should specify `npm install -g yarnpkg` not `npm install -g yarn`.
Lots of ways you can install Yarn over here: https://yarnpkg.com/en/docs/install
Yarn – A new package manager for JavaScript
11–20 of 486 posts
Re: Yarn – A new package manager for JavaScript
#12It 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-reg…
Huh, interesting! I thought this was going to just be a client. I wonder if it resolved to npm's servers or something.
A curl -I shows CloudFlare, at least. npm's does not. So it's at _least_ doing some sort of cache...
Re: Yarn – A new package manager for JavaScript
#13It 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-reg…
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.
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
#14I think the write-up should specify `npm install -g yarnpkg` not `npm install -g yarn`.
The yarn team has corrected the blog post[+].
[+] https://github.com/yarnpkg/yarn/issues/599#issuecomment-2529...
Re: Yarn – A new package manager for JavaScript
#15[deleted]
Re: Yarn – A new package manager for JavaScript
#16I wrote a post explaining why I'm psyched to be working on it:
TLDR:
- open, community governance that will support long-term evolution
- the technical details get a lot right out of the gate (decent performance, predictability, and security)
Re: Yarn – A new package manager for JavaScript
#17This looks awesome. But I have to wonder why create a whole new project rather than fork or upstream these changes to NPM? It doesn't seem like it's doing anything fundamentally different or outside of NPM's scope of responsibility.
Re: Yarn – A new package manager for JavaScript
#18It 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-reg…
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
#19"Linking: Finally, Yarn links everything together by copying all the files needed from the global cache into the local node_modules directory." Stop copying stuff. Just make it global and link. Next step is to make packages immutable and signed. I'm happy with this step and the fact that facebook will be able to push this.
This is something I really want to explore more through less-compatible modes. It was the original way yarn worked, but it wasn't compatible enough to be the default mode: https://github.com/yarnpkg/yarn/issues/57
Re: Yarn – A new package manager for JavaScript
#20It 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-reg…
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?