You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
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.)
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.
The text was updated successfully, but these errors were encountered: