3 ms·
The last time I tried async/await with Babel I had huge problem that my code was very hard to debug. When runtime error occurred it did not show any useful info
by Hurtak 11y ago
The last time I tried async/await with Babel I had huge problem that my code was very hard to debug. When runtime error occurred it did not show any useful information, like error line number, and thanks to transforming and regenarator-runtime wrapping of my code, it was nearly impossible to step through the code in any meaningful way, so I had to fallback to console log driven development.
Maybe something changed since the last time I tried, or perhaps i mis-configured something? How are error messages and debugging with this plugin?
- marten-de-vries 11y agoThe end result is more comprehendable than the regenerator output, but the code is still modified quite a bit to fit into a Promise chain structure. Some statement types (like loops) more than others (like a simple function call). I haven't paid special attention to source maps and the like yet apart from what Babel itself generates (which is quite a bit), so there's probably still quite a bit to gain here.