What is the easiest way to debug an error on RS?

Hey Kovid, it's been years since I've been developing with RapydScript and it really helps me in many things. Thanks for your work. Just one quick question, what's the best way to debug RapydScript errors? Especially the runtime errors not the compilation error (since the compiler points the direct code). Because first the javascript itself doesn't print the exact code line if the error is from a Promise, and then after searching for the code that cause the error with catch, it's a transpiled javascript which is harder to read for beginners (especially one who haven't know javascript or even new ES6 javascript developers can't seem to understand too). Because this bugs us a lot. It's actually not a problem for me but my colleagues depends on me in debugging the errors, I'm a bit confused about were they the one that weren't smart enough or I that was forcing them to use RS was silly.

This is actually a personal issue but I want to clear them up, do you have any suggestion? Maybe should I integrate RS to webpack? Or is it easy to add map files to RS?

The issue names no files, tests, or entry points. Start by locating RapydScript's transpilation workflow and checking how webpack integration or source maps could represent runtime errors; done means the project has a clearly documented, reproducible way to trace such errors back to RapydScript source.

Written by the indexing model from the issue text.