4 ms·
This is mostly a solved problem in regular compilers, and sourcemaps etc do currently exist for JS. I agree that the tooling/UI around this could be better, bu
by ratorx 2y ago
This is mostly a solved problem in regular compilers, and sourcemaps etc do currently exist for JS.
I agree that the tooling/UI around this could be better, but by focusing on this approach, things like Typescript get better as well.
- wiseowise 2y ago> sourcemaps etc do currently exist for JS. Are those being supplied with every website you use?
- ec109685 2y agoAre there debuggers that can single step over the transpiled bits so that it feels like the methods are implemented natively? Otherwise, it becomes a mess.
- ratorx 2y agoI’m not sure if it exists, but it definitely seems doable (a regular debugger has to map instructions to lines of code). If the browser starts treating JS as assembly, then there would probably be a greater onus for features like this.
- ec109685 2y agoThat would be nice. Was stepping through some modern react code, and the amount of cruft you see is terrible in the transpiled result.