WASM stack traces/debugging support in browsers (opens in new tab)

Hey, currently I have a project where I run some freestanding WASM blob in the browser. When it panics, firefox gives me nothing, but chromium gives me a stack trace of WASM addresses. I can use these with wasm-tools addr2line game.wasm 0xf00 to get the corresponding source location. This it quite annoying, but maybe nothing Zig can do about: apparently browsers only (want to) support mapping files, but LLVM only outputs DWARF information. Did anyone find a nice solution to this? I didn’t fin...