Corey Farrell

I'm sorry I don't use webpack so I can't make direct recommendations. If it's just a matter of getting the code instrumented then I assume webpack has a way to...

I'm not strictly opposed to this idea but we'd need to be sure that any options which can alter results (such as `--require`) are properly handled for cache invalidation.

I wonder if we add `nycInstrumentCache` to getInvalidatingOptions in lib/hash.js? This would force `nyc instrument` to cache to different filenames from normal nyc execution if. I assume you would use...

You must use [@istanbuljs/esm-loader-hook](https://github.com/istanbuljs/esm-loader-hook) to get coverage of node.js native ESM modules with nyc. You can feel free to use c8 if you wish but nyc will always be a...

Although the ES module system is considered stable loader hooks are a separate feature which are still very much experimental and expected to face breaking changes.

I just tested `node -r @babel/register --experimental-modules ./bin.mjs`, babel transformations did not happen. I'm sure they'll eventually get that working but until they do I don't think we should make...

@jrgleason that's not true with `"type": "module"` in your package.json `.js` files are intepreted as ES modules. That said the current status of node.js is that it doesn't support live...

You can tell nyc the directory to find `*.json` files with coverage: `nyc -t coverage_data report`. It's important that the directory not contain any `*.json` files that are not coverage...

Without a simple repository demonstrating the issue I cannot help you.

This is difficult to troubleshoot at this time. Current releases of jest still use istanbuljs modules associated with nyc 14, I've seem compatibility issues when trying to mix previous and...