istanbul: 1.0.0-alpha.2 : File [/foo/bar.js] ignored, nothing could be mapped

[yvele]

Running istanbul 1.0.0-alpha.2 on babel generated code with [source-maps] option set to (https://babeljs.io/docs/usage/cli/) both (babel 6.6.5, babel-core 6.7.2) I got many warnings like that:

File [/Users/Yves/foo/bar.js] ignored, nothing could be mapped

Here is how I run istanbul:

istanbul cover _mocha -- ./test --compilers js:babel-register \
   --require babel-polyfill \
   --require should \
   --require sinon

[codekirei]

Just ran into this as well. I believe it has to do with named vs anonymous default exports.

I put together a super simple example repo that reproduces this here.

• named — gets covered
• anonymous — throws File ... ignored warning and is not covered

My current workaround is to just structure my code with named exports.

[laggingreflex]

I'm getting this error in files whose only contents are named export statements, but of the following form:

/* eslint-disable */

// @create-index

export handle from './handle.js';
export throwEx from './throwEx.js';

(created via create-index).

On second thoughts, it kind of makes sense in my case as there's probably nothing to "cover" here.

[chalda]

any resolution to this? I don't want to create a massive commit changing every index.js export in my project...

[yvele]

I'm switching to jest: https://github.com/facebook/jest

[bengrunfeld]

@yvele after x hours (too embarrassed to say exactly how long) of trying to set up mocha and nyc to run the simplest possible unit test and generate a coverage report with ES6 import and export default, I tried going with your suggestion, and within 10 minutes, everything just freaking worked.

[yvele]

@bengrunfeld Yep it's way more easy.. jest replaces mocha, chai, istanbul, nyc, rewire.... and is way more powerful 😉

[alexgalin]

any update here?