<checks watch> oh, I see, it's time to rewrite my javascript builds again. My how the time flies.
But is this constant turnover getting ridiculous in the web dev & JS ecosystem?
Yes. I simultaneously credit and blame facebook for starting it with yarn; after yarn, the trend of re-writing build tools seemed to become much more acceptable and trendy, especially since yarn (at the time) was multiple times faster than npm; you could argue it was worth it. But now we've reached a stage where the diversity of tools like npm, yarn and pnpm, now tools like ni (https://github.com/antfu-collective/ni) are emerging to manage the diversity.
I think this is getting out of hand, now there are n+1 of them.
I call this the "JavaScript treadmill", where everything that's more than two years old is garbage written by nincompoops, but now we all got it right and now everything is fantastic, and the only people who criticize it are grumpy crusty old backend boomers too lazy to learn anything new.
If you go back in time two years, people said the same thing. And four years, and six years, etc.