James M Snell

I agree that we should be using `DOMException(AbortError)` to signal cancelations (or `DOMException(TimeoutError)` when `AbortSignal.timeout()` is finished. Having a separate `AbortError` that is specific to Node.js is confusing. Where Node.js...

I've said before, I'm +1 on this. I would extend it off the existing command line flag, e.g. `--no-warnings=DEP0111`. This makes it generic to all types of warnings that have...

> This doesn't really seem future-proof in a world in which we will eventually be able to transfer handles between threads. Will we? It's been discussed but I hadn't seen...

> ... that has consensus among collaborators beforehand. That's why this is all being done in the open with visibility through a draft PR.

> Well... in that case, what's the state that you eventually want to reach in terms of internal streams API? Let's start with a look at the external API then...

@nodejs/collaborators ... While this still definitely has a ways to go before it's ready to land (needs lots of tests and likely has quite a few bugs remaining)... I'm going...

That's the current thinking yes, but I plan to revisit that. It's not that different than what we have to do now except it's promise based instead of event based....

Here, I can bypass that question entirely by making it possible to provide your own low level consumer as opposed to getting either a node stream or web stream. The...

Quick update... I'll be working on this more next week to get unresolved comments resolved and get the CI passing so we can land. @mcollina @ronag and others... It would...

Resolved many of the outstanding comments and also added a detailed readme that should help with review.