Benjamin E. Coe

@LarsDenBakke it seems reasonable to me that our default behavior would be to `console.warn` what do you think? an error seems a little heavy handed.

@jamestalmage I like this idea, definitely an edge-case that it would be nice for spawn-wrap to handle.

@addaleax any thoughts about this old issue that's open on `nyc`?

Hey @nknapp @ErisDS, thought you might find this interesting reading (It's the version support goals I've been drafting for Node.js libraries at Google): https://github.com/googleapis/google-cloud-node#supported-nodejs-versions I'm working on a more thorough...

The opinion I've developed, as a library maintainer, is that 30 months is reasonable amount of time to support a Node.js version (which is the LTS length). It creates a...

@sirtimid this case should be covered by the test: https://github.com/istanbuljs/istanbuljs/blob/main/packages/istanbul-lib-instrument/test/specs/switch.yaml#L159C32-L159C82 Could you add an additional failing test if this is not the case?

I believe this was a change in design between Istanbul 1.0 and Istanbul 2.0? I'm not seeing `l` documented here: https://github.com/istanbuljs/istanbuljs/blob/main/docs/raw-output.md

Thanks for the feature request @sky-code, I've added to one of our backlogs.

> Same use case for us. @felipe-canopy hear you loud and clear, this is an interesting use case and something that we have on our minds. > Any expectations of...

@Angelodaniel what do you perceive the priority to be on this one? We're starting to gradually re-platform on a new data storage platform, which would likely not have this problem...