You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I understand that exclude-after-remap has been made default true in nyc@14. Upgrading broke coverage data collection for my TypeScript project; it was previously working fine in nyc@13.
I attempted to change the value of the exclude setting but it had no effect, even setting it to empty. Only setting exclude-after-remap to false fixes the issue, and it is not obvious why that's necessary in this sort of project.
The text was updated successfully, but these errors were encountered:
We're planning to add .ts to the default extension setting for nyc@15. Unfortunately this is a potentially breaking change so it cannot happen in nyc@14. You can follow #1103 for progress on this.
Link to bug demonstration repository
https://github.com/acchou/nyc-bug
This is a TypeScript project that demonstrates the issue. Instructions for reproducing are in the README.md.
Expected Behavior
Coverage information should be output when exclude-after-remap is true, because "exclude" is empty ([]) and no "include" is specified.
Observed Behavior
No coverage information is reported unless exclude-after-remap is set to false.
When upgrading from nyc@13 to nyc@14, the switch to exclude-after-remap to default true causes this issue to happen by default.
Troubleshooting steps
Environment Information
I understand that exclude-after-remap has been made default true in nyc@14. Upgrading broke coverage data collection for my TypeScript project; it was previously working fine in nyc@13.
I attempted to change the value of the
exclude
setting but it had no effect, even setting it to empty. Only setting exclude-after-remap to false fixes the issue, and it is not obvious why that's necessary in this sort of project.The text was updated successfully, but these errors were encountered: