> a strong argument against [...] things that require you to run a build on your front-end code Not really, if it's your own code that requires a build step, t

> a strong argument against [...] things that require you to run a build on your front-end code Not really, if it's your own code that requires a build step, then you control that build step and the tools and all and you can have nice auto-reload and fully working source maps and integration with all your other tools... Do whatever exotic build and transpilation makes you more productive when developing your application's code. But libraries and frameworks... it's not OK to have a large part of the ecosystem dependent on such build tools and at the same time have no usable tooling standardization to easily implement something as basic as "jump to implementation in original source".