-
Notifications
You must be signed in to change notification settings - Fork 868
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Source map support #260
Comments
There's not reason why we couldn't implement those in Rhino, but at the With that said, as I understand it, the Closure Compiler supports source https://github.com/google/closure-compiler/wiki/Source-Maps Perhaps someone from that team can help. On Fri, Jan 29, 2016 at 5:33 AM, Pavel Kukov notifications@github.com
Greg Brail | apigee https://apigee.com/ | twitter @gbrail |
Thank you @gbrail ! |
I landed here while looking for source map-driven exception stack traces, similar to node-source-map-support. TL;DR: source map-driven stack traces are impossible in Rhino. All source map-consuming tools need both the line and column numbers of the transformed code to retrieve the corresponding position from the original source. For example, Mozilla's own source-map expects the Rhino depends heavily on Java's own stack trace mechanism to generate JavaScript stack traces. See here where the built-in To make source maps work for stack traces, I expect we'll need to somehow attach column numbers to every JavaScript function and extract that information when constructing a stack trace. |
This is not an issue, it is question.
Did Rhino support source maps?
If not, is it planned?
The text was updated successfully, but these errors were encountered: