Benjamin Gruenbaum

Also maybe @isaacs since glob (minimatch) core inclusion will/may be discussed ?

@cspotcode yes that's a suggestion in https://github.com/nodejs/node/issues/44023#issuecomment-1205476021 :) Also making sure you don't miss the meeting doodle at https://github.com/nodejs/node/issues/44023#issuecomment-1205500132

One more ping to @nodejs/test_runner @cjihrig @aduh95 for the meeting doodle to make sure you saw it https://doodle.com/meeting/participate/id/dwjGRJmb

Hey, due to a combination of bereavement leave and food poisoning / tummy flu I've totally dropped the ball on this and won't be able to engage in the next...

CI is locked due to a security release - the process from now (sorry if this is stuff you know, telling you since it's your first code contribution here): -...

Hey, this is by design, you can see the context and meeting in https://github.com/nodejs/node/issues/36084. Node.js does throw `DOMException`s for DOM APIs. For its own APIs Node.js prefers a simpler AbortError...

> @benjamingr That design does not appear to have been revised when node added support for native DOMException. This is causing extra confusion, and the root of this issue. Node...

> Thanks for the thorough response, and good to know that there is still room for iterating the approach. Absolutely. > DOMException has only just been made public with node...

I think we are all very much in favor of standardizing third-party thrown exceptions and providing guidance to people authoring async APIs with cancellation. I think that's a good idea...

@domenic to be clear the thing blocking `DOMException`s for AbortErrors in Node.js isn't the fact people don't like `DOMException`s (we already ship `DOMException`s anyway). It's the fact `DOMException`s become a...