Corey Farrell

Note that istanbul-lib-instrument already supports ignoring nullish coalescing branches for non-transpiled code: ```js const a = b ?? /* istanbul ignore next */ c; ``` It's possible that `ts-node/register` might...

@pbn04001 this is not possible and no such option is planned. Nullish coalescing is an expression branch and if you don't exercise all of them you don't have 100% coverage....

@dhon istanbul does not support optional chaining at all. What you are seeing is the result of something else transpiling `?.` into conditional code, istanbul is then seeing that conditional...

We won't necessarily see the typescript annotations, possible we're only seeing the code which typescript generates. It's impossible to know what's going on without a very simple example but depending...

I'm not sure how this would be accomplished, maybe some kind of post-processing done after each HTML is generated to inline the style-sheets. Worth noting for projects with many covered...

I'm open to a pull request which would accomplish this as long as CSS is not inlined by default.

I think the issue is when istanbul instruments before `ts-node/register`. In that case `nyc-config-typescript` configures nyc to add the babel parser `typescript` but not `jsx`. So when it hits JSX...

I believe this is somehow caused by typescript, running your example code in pure JS does not cause this issue. May depend on your TS configuration. Note I've seen a...

This is likely due to transpiling to ES5. The ES5 code likely contains a generated branch which does not get covered.

> The coverage report for some reason highlights the return type annotation `ZXCVBNResult` is this the cause? What code is generated by `ZXCVBNResult`? It's possible this includes run-time type checks...