>Can't we just go back to node + npm + vitest + vite?
The mere enumeration shows how bad it is.
Why? Is fewer things always better? How far should it be consolidated? Taking it to an extreme, would having a tool named Everything that does anything you could imagine in relation to web dev be better?
Well, do one thing an one thing good as in Unix philosophy?
- Runtime
- Package manager
- Test runner
- Build tool
I think it's a pretty reasonable split of responsibilities, and not uncommon.
Eg: JDK + maven + junit + tomcat
Making these components pluggable is arguably how we get innovation (eg: yarn/pnpm, jest/vitest, etc)