Exactly. There's very good reasons why tools like Webpack and Babel exist. Here's two excellent articles that go over the history and use cases behind the JS

Exactly. There's very good reasons why tools like Webpack and Babel exist. Here's two excellent articles that go over the history and use cases behind the JS tooling ecosystem: http://tinselcity.net/whys/packers http://tinselcity.net/whys/packers https://www.swyx.io/writing/jobs-of-js-build-tools https://www.swyx.io/writing/jobs-of-js-build-tools As a counter-point, there's also valid reasons why a lot of the JS tooling ecosystem is painful to work with: https://increment.com/development/the-melting-pot-of-javascript/ https://increment.com/development/the-melting-pot-of-javascr... https://www.swyx.io/writing/js-tooling/ https://www.swyx.io/writing/js-tooling/ For myself personally, I'm quite happy with the React ecosystem. For the kinds of "desktop-app-in-a-browser" apps I work on, it's fantastic. (Caveat: I'm a Redux maintainer, so I'm also a bit biased here.)