Khafra

> It seems like this check is running unnecessary: AbortSignal has [kMaxEventTargetListeners] [set to 0](https://github.com/nodejs/node/blob/64ee8a025815553af30d9d273e2f2d07a5eb83ea/lib/internal/abort_controller.js#L181). This was changed a month ago and is currently only available in node v22.13.0+ and...

I submitted a PR to fix it, where I realized I added getEventListeners and therefore this bug. Whoops...

@lucacasonato why does the webidl async iterable type fallback to using Symbol.iterator? Wouldn't the issue be solved by *not* doing this - even if it goes against precedent? Right now...

It's already possible to support async iterables in a spec compliant and cross-platform way as mentioned above, via ReadableStream.from. Adding in a new, non-spec api for better performance is a...

I was following Matteo wrt performance, but there is still a rather large issue not being mentioned. - node does **not benefit** from removing async iterable support. - webidl limitations...

I have actively been working on reducing our fetch's incompatibilities with the spec, but I cannot see any benefit for our users by removing this right now - once we...

> (We attempted to ship the PR experimentally in the last release, but had to revert because it was incompatible for existing users, like Hono users: https://github.com/denoland/deno/issues/25278) It was compatible...

1. We would be warning people using node 18 not to use something that has no alternative (unless we consider polyfilling ReadableStream.from an alternative...). Would we only be warning v20+...

Deno has re-added support for async iterables. I think we can close this now? https://github.com/denoland/deno/pull/26882 Please reopen if there's more we need to discuss here.

HeadersList should not be exposed.