Corey Farrell

This would be a massive breaking change, I'm not sure if it's even possible. Changing functions from sync to async cause ripples across the code. This would require every function...

@SimenB No possibility of instrumentation becoming async as long as `require` API exists. Thanks for the feedback about the reporting API.

To my knowledge this is (or was) a change in node.js, not nyc. Does your file have a byte order mark? If so that is not valid and is no...

A small demonstration in a git repository would be useful. I just tested by creating script.cjs: ```js #!/usr/bin/env node console.log('hello'); ``` The following worked: ``` chmod +x script.cjs ./script.cjs &&...

I'm not able to reproduce the error with the linked repository. I did the following using node.js v10.15.0: ```sh git clone https://github.com/fabriciojso/monetify-imagini cd monetify-imagini npm i npm t ``` The...

This is actually an issue with istanbul-lib-instrument so I've transferred the issue to our monorepo.

```js // NOT the same as optional chaining const status1 = error.response && error.response.status; // Optional chaining const status2 = error.response?.status; // Transpiled optional chaining (approximate) let response_; const status3...

Can you comment with an example of output from typescript for the following: ```js /* before const */ const a = /* before b */ b /* before ?? */...

I don't think istanbuljs is able to support coverage hints in the code generated by TypeScript for these new JS features. The only suggestion I can provide right now is:...

Any change to `istanbul ignore` hints is high risk and complex. I don't have time to go down this rabbit hole, I'm not sure istanbuljs can produce better results from...