Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Yarn 1.0: Workspaces, auto-merging lockfiles, selective versions resolutions

code.facebook.com

Post reply on HN
Print view View original

1–10 of 48 posts

Re: Yarn 1.0: Workspaces, auto-merging lockfiles, selective versions resolutions

#2

Post by orta »

A big congrats are in order. Yarn came out just as I started working in the node ecosystem, and it fixed nearly all my dependency manager problems.

Since then it's evolved and it's really helped provide a counter to npm offering different design choices but working together where it counts. It's the 4th most popular brew dependency and ~25% of npm downloads. People love it.

Congrats Yarn team - you've been doing a great job.

* https://stats.yarnpkg.com * https://brew.sh/analytics/install-on-request/

Re: Yarn 1.0: Workspaces, auto-merging lockfiles, selective versions resolutions

#3

Post by adamgiacomelli »

I have had a failed heroku deployment because of yarn 1.0 yesterday - quite interesting. Made me define the yarn version in package.json. I have also had some problems with the yarn repo being unavailable a couple of months ago.

That being said - I have migrated to it completely on all projects and never looked back - so yay for yarn!

Re: Yarn 1.0: Workspaces, auto-merging lockfiles, selective versions resolutions

#4

Post by BYK »

adamgiacomelli wrote: post #3

I have had a failed heroku deployment because of yarn 1.0 yesterday - quite interesting. Made me define the yarn version in package.json. I have also had some problems with the yarn repo being unavailable a couple of months ago. That being said - I have migrated to it completely on all projects and never looked back - so yay for yarn!

We have patched that issue and already tagged 1.0.1 ;)

Re: Yarn 1.0: Workspaces, auto-merging lockfiles, selective versions resolutions

#5

Post by BYK »

BYK wrote: post #4
adamgiacomelli wrote: post #3

I have had a failed heroku deployment because of yarn 1.0 yesterday - quite interesting. Made me define the yarn version in package.json. I have also had some problems with the yarn repo being unavailable a couple of months ago. That being said - I have migrated to it completely on all projects and never looked back - so yay for yarn!

We have patched that issue and already tagged 1.0.1 ;)

See https://github.com/yarnpkg/yarn/issues/4320

Re: Yarn 1.0: Workspaces, auto-merging lockfiles, selective versions resolutions

#6

Post by nailer »

I've been holding off on yarn since npm v5 has some big performance increases, but there's (as of npm 5.3) still an issue where npm v5 deletes all `private: true` packages - we've had to revert to 4.6 - and I'm a little worried a data-loss issue isn't being treated as severe.

Re: Yarn 1.0: Workspaces, auto-merging lockfiles, selective versions resolutions

#7

Post by brad0 »

orta wrote: post #2

A big congrats are in order. Yarn came out just as I started working in the node ecosystem, and it fixed nearly all my dependency manager problems. Since then it's evolved and it's really helped provide a counter to npm offering different design choices but working together where it counts. It's the 4th most popular brew dependency and ~25% of npm downloads. People love it. Congrats Yarn team - you've been doing a gr…

I jumped on node around the same time and I've come to an opposite conclusion.

The things I liked was the offline cache and the yarn integrity.

However there was just too many issues regarding its dependency on npm and not playing nice with other tools such as brew.

I dove into the code to try and fix these issues but both the quality of the code base and the politics going on in the issue tracker turned me off very quickly. [1]

If yarn had been approached with more senior developers I think it could have replaced npm entirely.

[1] https://github.com/yarnpkg/yarn/issues/2064

Re: Yarn 1.0: Workspaces, auto-merging lockfiles, selective versions resolutions

#8

Post by allover »

nailer wrote: post #6

I've been holding off on yarn since npm v5 has some big performance increases, but there's (as of npm 5.3) still an issue where npm v5 deletes all `private: true` packages - we've had to revert to 4.6 - and I'm a little worried a data-loss issue isn't being treated as severe.

Deletes them in what situation? Can you provide a link?

Re: Yarn 1.0: Workspaces, auto-merging lockfiles, selective versions resolutions

#9

Post by [deleted] »

brad0 wrote: post #7
orta wrote: post #2

A big congrats are in order. Yarn came out just as I started working in the node ecosystem, and it fixed nearly all my dependency manager problems. Since then it's evolved and it's really helped provide a counter to npm offering different design choices but working together where it counts. It's the 4th most popular brew dependency and ~25% of npm downloads. People love it. Congrats Yarn team - you've been doing a gr…

I jumped on node around the same time and I've come to an opposite conclusion. The things I liked was the offline cache and the yarn integrity. However there was just too many issues regarding its dependency on npm and not playing nice with other tools such as brew. I dove into the code to try and fix these issues but both the quality of the code base and the politics going on in the issue tracker turned me off very…

[deleted]
Post reply on HN