Open MatthiasF999 opened 8 years ago
That message usually means that the source text for a file does not match what was instrumented.
Is there a way you can provide a basic failing case in a gist or something?
Well, I found the mistake.
It is a problem with babel not generating sourcemaps when not told via command (.babelrc doesn't work in this case).
have the same issue +1
@MatthiasF999 How did you solve?
You need to remove
"sourceMaps": true
from the .babelrc file. That solved it for me.
I have the same issue and don't have "sourceMaps": true
in my .babelrc file.
In my case this problem was casused by running istanbul after browserify-ngannotate in browserify transforms.
I created a patch for this issue: https://github.com/istanbuljs/istanbul-reports/pull/10
For those working with webpack, you can find this useful:
https://github.com/deepsweet/istanbul-instrumenter-loader/issues/32
Basically work with older version of "istanbul-instrumenter-loader": "0.2.0"
I ran into this problem in my Webpack setup. Making istanbul-instrumenter-loader
the inner most (last) loader in the chain for my files helped make it work. Also I added sourceMaps: true
as a babel option. This is using istanbul-instrumenter-loader
2.0.0.
Trace
relevant package.json
I can only test this with istanbul@next, since the stable version delivers an empty coverage report.