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

11–20 of 48 posts

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

#11

Post by nailer »

allover wrote: post #8
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?

There's a couple of similar deletion issues, they're all linked from https://github.com/npm/npm/issues/17929, the deleting private one happens in all situations, eg just an npm install, see https://github.com/npm/npm/issues/17927

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

#12

Post by nwlieb »

This is fantastic! The biggest standout feature in my opinion is workspaces. I've been using workspaces on a client project with many sub-projects and it has been a pleasure.

Shared modularized code without creating private npm packages or doing some "linking" magic has been wonderful for productivity. It's as simple as creating another local package and symatically everything else has remained the same as a regular npm package, plus the benefits of having immediately updating code. For anyone with a large modular codebase wanting to forray into a monorepo approach I highly recommend checking it out. They also released a blog post here detailing the feature: https://yarnpkg.com/blog/2017/08/02/introducing-workspaces/

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

#13

Post by arcatek »

nwlieb wrote: post #12

This is fantastic! The biggest standout feature in my opinion is workspaces. I've been using workspaces on a client project with many sub-projects and it has been a pleasure. Shared modularized code without creating private npm packages or doing some "linking" magic has been wonderful for productivity. It's as simple as creating another local package and symatically everything else has remained the same as a regular…

We've also published a more detailed documentation here: https://yarnpkg.com/en/docs/workspaces!

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

#16

Post by petetnt »

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…

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

The biggest reason by far why Yarn got so popular so quickly was because it didn't come and try to split the existing ecosystem but chose build on top of npm's foundation with ways that npm didn't (at that point) offer instead.

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

#18

Post by brad0 »

petetnt wrote: post #16
brad0 wrote: post #7

Earlier quoted context omitted.

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…

> If yarn had been approached with more senior developers I think it could have replaced npm entirely. The biggest reason by far why Yarn got so popular so quickly was because it didn't come and try to split the existing ecosystem but chose build on top of npm's foundation with ways that npm didn't (at that point) offer instead.

Yes I agree! I didn't really make myself clear.

I feel that if yarn kept its strategy but had more senior developers writing the core software I think it could have been able to outpace npm in terms of features and speed.

If this had have been the case then it wouldn't make sense to use npm at all. Yarn would be faster and have more features.

From my experience I feel that yarn isn't offering much value now and the codebase quality means that future features will take too long to build.

Post reply on HN