gopherjs serve: Display compilation errors in browser console. #232
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This is nice when using with gopherjs serve, because it already recompiles on browser refresh. This allows one to switch between code editor and browser for a faster iteration cycle. No need to also switch to the terminal to see errors, as now both compilation and runtime errors are visible in browser console.
|
A possible future enhancement here is to make use of source mapping to have the browser display compilation errors in the actual Go code. I'm not very familiar with the details of how source mapping works, but I think it can be done. |
neelance
added a commit
that referenced
this pull request
May 31, 2015
gopherjs serve: Display compilation errors in browser console.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This is nice when using with gopherjs serve, because it already recompiles on browser refresh. This allows one to switch between code editor and browser for a faster iteration cycle. No need to also switch to the terminal to see errors, as now both compilation and runtime errors are visible in browser console.
I'm backporting some enhancements from my
gopherjs_serve_htmltool, so I can stop using it and rely ongopherjs servefull time.This resolves a future enhancement that was mentioned in #121 (comment).