Skip to content
This repository has been archived by the owner on Jan 21, 2024. It is now read-only.

Adventurous new feature: Add support for source maps? #61

Open
JamesMGreene opened this issue Jan 23, 2014 · 5 comments
Open

Adventurous new feature: Add support for source maps? #61

JamesMGreene opened this issue Jan 23, 2014 · 5 comments

Comments

@JamesMGreene
Copy link

Adding support for getting cleaner stack traces from minified JS files via source maps would be pretty amazing.

Can leverage mozilla/source-map project for decomposing sources in ES5-compliant browsers.

@RickWong
Copy link

👍 Would love this feature.

@leobalter
Copy link

Please remember to tell on qunitjs/qunit#590 if you get this working. It's really interesting and if you need help at some point, count on me.

@JamesMGreene
Copy link
Author

Also, taking a look at fresheneesz/stackinfo and fresheneesz/deadunitCore might be beneficial.

stackinfo wraps stacktrace/stacktrace.js to cleanly extract line and column numbers of Error objects. One feature of deadunitCore combines the use of stackinfo and mozilla/source-map to get stack traces that honor source mapping.

@niemyjski
Copy link
Collaborator

Any progress on this?

@niemyjski
Copy link
Collaborator

@JamesMGreene I'm helping maintain TraceKit upstream.. If you want to recreate this issue s in the master (https://github.com/csnover/TraceKit) I'll participate in the discussion and see if we can make this happen.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants