Post

Maël Nison
@mael.dev

Outside of that it's just the codename for this new codebase, same as Berry was the codename for the TS one.

Wojciech Maj
@wojtekmaj.pl

TBH from my experience it's irrelevant at this point. All package managers except for npm have reached the point of diminishing returns. Yarn v4 installs my (rather large) repo in 4.2 seconds on a mediocre CI worker. Even a 10x improvement, while definitely impressive, would not be life-changing.

Jonas Røssum
@nimrossum.com

Why even include a benchmark in the post if you're going to leave out Bun? It feels like benchmarking a modern car against a horse just to show the car is fast. If we're talking about 'diminishing returns,' you have to test against the current ceiling, not just the floor.

Wojciech Maj
@wojtekmaj.pl

One good reason not to include Bun is that you'd be comparing apples to oranges. Bun "cheats" by only running postinstall on a predefined list of packages they deemed "safe". It also caches stuff aggressively leading to behavior differences when compared to other package managers.

Abdel
@abdelelmedny.bsky.social

Awesome work! Im curious what the "before" column in the comparison table represents. Im assuming yarn 4? I look forward to yarn 6 first stable release! Thanks

Philippe Serhal
@philippeserhal.com

Hey @mael.dev, congrats! You all had reached out about Yarn 6 support on the Netlify build system a few months ago. Did that end up working itself out because you decided to keep supporting corepack? Let me know if there's anything we can do here!