Jeff Rifwald

@MoonTahoe I believe your issue is being caused by the babel source map no longer being correct. Anything that "makes it work" other than fixing the source map is at...

If you dig into the code generated by babel at the `import * as React from 'React';` line, you'll find the mystery branches live in that code. I'm not sure...

I am suspecting something strange could be happening in your filesForCoverage setup step. Perhaps try omitting that part to see if it helps. I'll go ahead and update the babel...

@ryanzec The preferred method of making sure all files are covered is using a common `root` setting and using the `include-all-sources` flag either on the command line or in your...

Also, one other thing you can try is `import React from 'React';` instead of `import * as React from 'React';`. The star import produces a lot more code than the...

Your only option here is to look at the generated code and try to figure out why it is doing what it is doing. Babel is literally creating statements that...

@silkentrance @ryanzec I actually have not been able to get completely correct coverage from babel-istanbul, isparta, or istanbul's aphla. I believe there is just some inherent weirdness with the source...

Sorry I missed this issue. See my response to a similar issue here: https://github.com/jmcriffey/babel-istanbul/issues/85#issuecomment-425529196

I believe this means the transformer added a branch but did not tell the source map generator about it. `6.14.0` added some checks to classes to allow them to be...

This is likely the culprit: https://github.com/babel/babel/pull/3527/files#diff-f78a336b572b82483a318406b52dd27dR349