Wonderful post, but I think it misses the point a little bit. What angers me to use node on automated tests on the browser is not only how fragile the tooling is - but the fact that you are, essentially, using a different language and runtime than what your app will run

Like, you will run your code in Firefox / Safari / Chrome, so you use... node... to test it? Without a browser? With mocked web APIs? Stuff that only works in Node?

I agree with the post, but I think the pitch is higher - as an example, I was working with Typescript recently and while I was discussing the pain points of the tooling with a friend, I mentioned Pulsar. And he asked me where did I pull strength to work on a Node.JS project at my free time. And then, I answered - "well, Pulsar doesn't use any build tool, no webpack, no Babel, nothing of these - it's just "write Javascript and thing will work as expected". And he was 🤯, saying "I completely forgot that this is a thing that you can do!"