Node extensions

[ronag]

What extension to the spec (for a "non-strict" mode) do we believe makes sense for usage in node?

Some things I can think of:

• Accept AsyncIterable (including stream.Readable) and Iterable as Request body. (Allow request take AsyncIterable body? whatwg/fetch#1291)
• Accept flat raw headers array for Headers.
• Accept EventEmitter as AbortSignal.

[ronag]

@Ethan-Arrowood @szmarczak

[szmarczak]

Accept AsyncIterable (including stream.Readable) and Iterable as Request body.

👍

Accept flat raw headers array for Headers.

Why?

Accept EventEmitter as AbortSignal.

Why?

[ronag]

Accept flat raw headers array for Headers.

Why?

Performance

Accept EventEmitter as AbortSignal.

Why?

Not sure. A lot of node libs seems to do this. Maybe support for node versions without AbortSignal?

[szmarczak]

Performance

Have you benchmarked this already? I don't think this will matter given the overhead...

Maybe support for node versions without AbortSignal?

Isn't fetch already Node.js 16+?

[ronag]

Performance

Have you benchmarked this already? I don't think this will matter given the overhead...

@Ethan-Arrowood Did some work on this. It's mostly for the cases where the headers are already in that format, e.g. node core rawHeaders or headers from undici core api. So I guess it's not just perf it's also compat.

Maybe support for node versions without AbortSignal?

Isn't fetch already Node.js 16+?

Yep. So maybe not relevant.

[szmarczak]

It's mostly for the cases where the headers are already in that format

👍