I made a simple demo: source, deployed
Build command: GOOS=js GOARCH=wasm tinygo build -o main.wasm ./main.go
I was hoping anyone going to this page could see the main.go in the browser developer tools; however, the source is referred to with the file:// protocol, so it can only be retrieved if on my machine.
Is there any way to make the debug info tinygo emits either 1) embed the source text in the WASM or 2) reference a resource relative to the WASM file, rather than file:// (so that the webserver could provide the source alongside the wasm)?
(aside: I made this demo as part of reporting an issue with debugging to Chrome DevTools: https://buganizer.corp.google.com/issues/463803622)