You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
guybedford
changed the title
Show JS source in errors
Show JS source frames for errors
Aug 30, 2024
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.
The text was updated successfully, but these errors were encountered: