Join GitHub today
GitHub is home to over 50 million developers working together to host and review code, manage projects, and build software together.
Sign upGitHub is where the world builds software
Millions of developers and companies build, ship, and maintain their software on GitHub — the largest and most advanced development platform in the world.
Some areas of the generated JS files are not covered by source maps. #943
Comments
I dug into the isse a little bit today and it looks like the source map support is working, but I got lucky enough to get a stack trace which lands into areas of the compiled code which are not mapped onto any original Go code. For example:
I used https://pastcompute.github.io/ScriptMapper/ to decode the source map and this is where this line ends up pointing at:
The generated script:
This code looks like some sort of GopherJS-generated package preamble, which is probably why it isn't mapped directly on the original source code. It would be nice, however to have it mapped at least into the file it was generated for. |
Hi folks, I was trying to see if I can help with Go 1.13 support, but I can't get source-map-support to work properly and deciphering stack traces is becoming difficult :/
My steps:
Note there isn't a warning about missing source-map-support module. It would be there if I didn't do the
export NODE_PATH=...
thing.I also tried this:
The result is exactly the same.
For the reference, the compiled scripts: fmt_test.zip. Manual inspection doesn't seem to reveal any smoking gun.
Any suggestions? Thanks! :)