Lots to unpack here. Modern JS going just great.

This situation is avoidable

https://dev.to/thejaredwilcurt/bun-hype-how-we-learned-nothing-from-yarn-2n3j

Bun hype. How we learned nothing from Yarn

Here we go again, making the same mistake. I'm constantly reminded that every 5 years the amount of...

DEV Community

@brianleroux OK I'm in like broad agreement, but also there's no reason to believe npm would have gained those features or gotten so much faster if yarn were not around, and plenty of reason to believe the opposite.

I can buy the conclusion, but also I think the author should have considered that idea.

Bun has got some traction because it is attacking real problems that people are suffering from - I hope the same thing happens and the mainline improves after seeing that.

@llimllib respectfully disagree. npm didn't have big problems as I remember it, but the fb marketing team certainly made it sound like it, and there is lots of evidence that technology trends to faster/cheaper (aka industrialization)

@brianleroux when yarn came out, my team switched because npm's slowness was killing us and yarn was free money. I wish I had the numbers handy for how much faster it was, but it was significant.

I am glad npm has improved in the meantime, it's what I use now that they've equalized