bytecodealliance / bytecodealliance/StarlingMonkey
Show JS source frames for errors
Open
- Dominant language
- C
- Stars
- 288
- Forks
- 57
- PR merge metrics
- No merged PRs in 30d
Description
Since the JS source code string remains in Wasm memory, there's no reason we can't improve error reporting to include a proper source code output frame.
This would be a tremendous boost to debugging JS, especially for Fastly, where we run the JS code through a build step before executing it that suffers from not support source maps currently.
Contributor guide
No contributing guide indexed for this repository
Assessment
This issue has not been assessed yet.