Comment #4 on issue 3652 by [email protected]: Sourcemap'd stacktraces
https://code.google.com/p/v8/issues/detail?id=3652
I can chime in here. I'm the original author of
https://github.com/evanw/node-source-map-support/, a library which tries to
patch this behavior into the VM as best it can using
Error.prepareStackTrace. It sort of works but isn't ideal because 1) it's a
global handler that you need to coordinate between the libraries you depend
on, 2) it uses SJAX which seems like it may be removed from the web
(https://www.w3.org/Bugs/Public/show_bug.cgi?id=28505), and 3) it relies on
internal implementation details of V8.
It would be awesome if V8 implemented this and my library is no longer
needed. It seems pretty clear at this point that compiling to JavaScript is
a core part of building software for the web and it's a shame that the lack
of tooling support in this area makes life unnecessarily difficult. Plus,
if V8 led the way here, it would be easier to convince other VMs of the
usefulness of this feature. It's currently impossible to patch this into
other VMs because they didn't have the foresight of making a useful API
like Error.prepareStackTrace.
See also: https://code.google.com/p/chromium/issues/detail?id=376409. Right
now source maps "work" in Chrome by DevTools translating them in the UI,
but this isn't a solution because all uses of the "stack" property are
still incorrect.
--
You received this message because this project is configured to send all
issue notifications to this address.
You may adjust your notification preferences at:
https://code.google.com/hosting/settings
--
--
v8-dev mailing list
[email protected]
http://groups.google.com/group/v8-dev
---
You received this message because you are subscribed to the Google Groups "v8-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
For more options, visit https://groups.google.com/d/optout.
