I believe that having a proper way to track down stack traces into Rust code in browser DevTools. I've found this tool that generates a .map file that the browser can use to match js and wasm to rust code: https://github.com/mtolmacs/wasm2map. This tool can be used as a library or a CLI tool.
Proposal
Embed wasm2map in trunk, and adding a new step that generates the .map file to allow the browser devtools to correlate stacktrace addresses with rust source code file and lines.
After some investigation, I've discovered that there is a pending feature in walrus that would allow wasm-bindgen to generate binaries while keeping the debug information up to date.
I believe that having a proper way to track down stack traces into Rust code in browser DevTools. I've found this tool that generates a .map file that the browser can use to match js and wasm to rust code: https://github.com/mtolmacs/wasm2map. This tool can be used as a library or a CLI tool.
Proposal
Embed wasm2map in trunk, and adding a new step that generates the .map file to allow the browser devtools to correlate stacktrace addresses with rust source code file and lines.