Corey Farrell

nyc does not yet support coverage of node.js native ESM. It will take some time as node.js has just created API's to make this possible though they are still experimental...

For anyone interested please see https://github.com/istanbuljs/esm-loader-hook#readme. To be very clear this is experimental.

This will not be considered until after the node.js loader feature is no longer experimental.

This issue is about node.js native ES modules, if you are using the user-space `esm` module or babel then you are not experiencing the same issue.

@pandres95 it's a complex set of issues being worked in node.js itself, there is nothing to be done on this end. It's not possible to accelerate progress . I fully...

> I tried using `c8`. However seems to be failing a bit. I'm sure @bcoe would appreciate a report on c8 if you can provide a reproduction.

To my knowledge the situation has not changed, the specific issue is that ESM loader hooks need to be stable. This is a separate feature on top of ESM itself.

Yes, we expect the `--loader` feature to have breaking changes. There are active discussions in the nodejs repository about completely breaking the existing loader (this is allowed as they are...

You can use [c8](https://github.com/bcoe/c8/) instead of nyc or follow the instructions at [@istanbuljs/esm-loader-hook](https://github.com/istanbuljs/esm-loader-hook/) to get coverage from nyc on projects with `"type": "module"`. To repeat myself, the `--loader` feature is...

Please upgrade babel-plugin-istanbul and istanbul-lib-coverage to the `next` versions otherwise you are combining multiple versions of istanbul libraries. Once you've done that assuming this is still an issue can you...