3 ms·
The shock wave that TS sends through a JS stack is hard to ignore. It's really annoying. Every tool added TS support in a slightly different way and you always
by city41 5y ago
The shock wave that TS sends through a JS stack is hard to ignore. It's really annoying. Every tool added TS support in a slightly different way and you always have to keep it in mind no matter what you're doing. Sadly it's just the reality we gotta face. I'm hoping Rome can live up to the hype and be helpful here.
- dvt 5y agoOh man, so true, between TS mangling and whatever framework you're using (Vue/React/etc.), the stack trace ends up being literally worthless. It's kind of funny to think about: when something goes wrong, I don't even look at the trace (which is 100% what you'd do in any sane language), but rather I just go back and look at the "last thing I changed."
- city41 5y agoAh that is true as well. When I said stack I meant like Babel, Storybook, Webpack, Jest, etc. But yeah JS stack traces aren't so fun these days.
- Oddskar 5y agoYou aren't using source maps to transform your stack traces then? I've had very little issue in understanding stack traces in any of the major JS frameworks.
- adamscybot 5y agoI think esbuild is basically already doing most of what Rome promises
- inbx0 5y agoFrom Rome readme: > Rome is designed to replace Babel, ESLint, webpack, Prettier, Jest, and others. Afaik esbuild only intends to be a replacement for 2 out of 5 of those things. It does that well for sure, but if parent commenter's main issue is the amount of different tools, I don't think esbuild will help.