Benjamin E. Coe

We should probably loop @MylesBorins into this conversation as well, curious what his thoughts are.

👋 having worked on Istanbul for years, the lack of source-map support in transpiled code was really bugging me, guess what, we've built initial support into Node.js now for this:...

:wave: topics are new to me, have never configured them on my repos. I'm happy to add some, is it something you have permission to do? or do you need...

I feel like `PATHEXT` *might* be fixed, or at least I saw a bug issue on Node.js closed related to it... @satazor thanks for the list, it's basically a laundry...

@satazor we referenced this issue for `PATHEXT` in the doc, which has since been closed: https://github.com/nodejs/node-v0.x-archive/issues/2318

@sindresorhus @ehmicky, I'd advocate that we write-up a proposal [here](https://github.com/nodejs/tooling) under initiatives, which outlines some of the issues being shimmed by exec alternatives; some of these cross-platform issues (I think)...

>I'm a little concerned that yargs/lib/apply-extends isn't a public API. If it isn't, maybe we can vendor it (e.g., just copy/paste it into a function in lib/cli/options.js). @bcoe can you...

> AFAICT you are free to use applyExtends Yes, my intention was that it's a blessed public helper now. The caveat is that [we need to fix this](https://github.com/yargs/yargs/issues/1789).

@mf-pherlihy [email protected] introduces ESM, and was a somewhat major shuffling around of code. I'd be interested in making sure we address any issues you're bumping into with tests.

> I do not consider the new behavior as a bug, it seems more consistent now than before. @juergba that's good to hear 👍 Sound like we perhaps just need...