Ember-cli: Getting qunit's stack trace to use sourcemaps

[bcardarella]

I realize this is beyond the scope of ember-cli but I thought this would be a good place to start the conversation. It would be very nice if we could coerce QUnit's stack traces to give the file path + line number from the source maps rather than from vendor.js or app.js

Any thoughts on if this is possible? /cc @ef4

[ef4]

I have a partial solution to this problem in my mocha reporter (https://github.com/ef4/better-mocha-html-reporter).

It puts a link next to each stack trace that dumps it to the console on demand. The console automatically sourcemaps it.

To sourcemap them directly in the page you'd need to implement the whole lookup process. The browser doesn't expose that capability.

On Mar 11, 2015 12:37 AM, "Brian Cardarella" [email protected]
wrote:

I realize this is beyond the scope of ember-cli but I thought this would
be a good place to start the conversation. It would be very nice if we
could coerce QUnit's stack traces to give the file path + line number from
the source maps rather than from vendor.js or app.js

Any thoughts on this? /cc @ef4 https://github.com/ef4

—
Reply to this email directly or view it on GitHub
https://github.com/ember-cli/ember-cli/issues/3499.

[stefanpenner]

would be cool, but out-of-scope for now. Feel free to continue the conversation though.

[cs3b]

Just got in to this ticket when doing research (I will leave here a link that might help in implementing this)

https://github.com/novocaine/sourcemapped-stacktrace

[stefanpenner]

@cs3b i would recommend continuing discussion on the QUnit repo

[stephanebruckert]

I'm using https://github.com/san650/ember-qunit-source-map and it helps a lot