Skip to content
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

Support separate source map files #14

Open
rmehlinger opened this issue Jul 7, 2017 · 1 comment
Open

Support separate source map files #14

rmehlinger opened this issue Jul 7, 2017 · 1 comment

Comments

@rmehlinger
Copy link

Currently, the package requires that source maps be inline. However I'm using Babel rather than Browserify, and generating separate source map files. As a result, I have to run my babel compilation twice--once with inline maps for the benefit of Karma, and once with maps sent to separate files, for the main release. It'd be nice if instead I could have Karma reference separate map files.

@lddubeau
Copy link

lddubeau commented Oct 5, 2017

Did you actually try it? I'm using it with a setup where I compile TypeScript to JS, with separate .map files, and it is working just fine after installing karma-source-map-support: the stack traces reported through Karma point back to the TypeScript code. (In case there's any doubt: before I installed karma-source-map-support the traces were pointing to the compiled JS code.)

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

No branches or pull requests

2 participants