Corey Farrell

I use hints in sources processed by `babel-plugin-istanbul` so I know it can work (the sources I'm processing include ESM and async/await). If someone can post a bug demo repository...

I think this is not intended, is probably a bug in istanbul-lib-instrument. CC @bcoe @JaKXz do you agree?

I've transferred this issue to the istanbuljs monorepo so it can get more visibility and this is where the fix will have to be made. Also updated the title to...

This strikes me as possibly an issue with the source-maps being generated. If src/Component.vue has a source-map that refers to `src/Component.vue` that is incorrect, it should be `Component.vue` (alternatively istanbuljs...

From what I can tell the changes being requested here would break projects that construct correct source-maps. Can someone commit generated files to a git repo so I can browser...

Related: #273

Can you try again with the latest `jest`? The version of jest you linked uses an older version of istanbul with babel 6, the current version of `jest` uses current...

I can confirm this issue, this is why nyc 15 now ignores coverage generated by `all: true` for files which were actually tested. This caused issues when the tests ran...

From what you're showing this line should be considered both a branch `if (!scheduledEvent)` and a statement `return [3 /*break*/, 4];`. To triage this issue we will need to see...

@JaKXz https://github.com/RoniSegal/missing-branch-coverage was provided - the link is easy to miss in @RoniSegal's comment from two days ago.