-
Notifications
You must be signed in to change notification settings - Fork 79
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
remap-istanbul unable to find sourcemaps #96
Comments
@gschambial does a source map for |
For me the same. |
This should be fixed with #87 ... we just need to wait for a release. |
I don't know, probably I'm drunk, but I'm having the same problem 'Error: Could not find source map for: ' also with the latest release of remap-istanbul (0.8.0). |
Karma coverage does not create the needed source maps. Update: Karma-coverage-istanbul still requires remap-istanbul 0.7 and therefore, does not use the new features. We have to wait for another release sshev/karma-remap-coverage#10 |
Initial answer: I'm using istanbul-instrument-loader but I'm having the same problem. Updated answer: Damn :( |
Works now for me... |
👍 We'll wait for any further feedback before closing this issue in case there's anything else we might have missed. |
It's not working in one of my personal projects. I also tried to copy and paste @MichaReiser's config from parallel.es, but without success.
I'm confused |
@Ks89 I can imagine the following issues:
|
Yes The project is open source. I created a branch for this. |
The problem is simple to solve and has nothing to do with *istanbul. You might have noted that only the source maps for typescript files are missing. So it must have something to do with your TypeScript configuration ;) I studied your webpack.configuration and surprisingly, you disable Source Maps for TypeScript! So there are actually no source maps for the TypeScript code... {
test: /\.ts$/,
loader: 'awesome-typescript-loader',
query: {
module: 'commonjs',
sourceMap: false,
inlineSourceMap: true
}
} So just remove the two source map lines from the configuration and everything works smoothly. |
Oh Damn. Thank u. So simple? I'll try this evening. |
I confirm, everything is ok now. |
Thanks everyone for your attention, patience and help! Closing this one out, hopefully for good. |
I am still getting the same error after changing version to:
My karma.conf.js:
...and my tsconfing.json:
|
I am trying to generate coverage report of
TypeScript
Files usingkarma-remap-istanbul
plugin.My test cases are being executed successfully by karma, but when karma-remap-istanbul is trying to generate coverage report, it is throwing following error:
My configuration files are as follows:
karma.conf.js
webpack.test.js
package.json
Any kind of help would be highly appreciated.
The text was updated successfully, but these errors were encountered: