Khafra

cause is fine. The error message is fine too and should be kept.

@jawj don't worry about it at all, I should have explained why we used DataViews since you asked in the PR, but I didn't. There aren't currently benchmarks so there's...

the actual implementation deviates from the spec (adds `innerFetch`, adds a new deferred promise/context object, etc.)

one of the biggest concerns is the end channel, which doesn't publish a message when the fetch ends, but is actually being done after a request has started: ```js function...

Yes it's prescriptive, but it makes maintaining fetch easier. For example, when the spec mentions "fetch", it will no longer be "fetch" in undici, but "innerFetch". Then there's also the...

which is years away from being stable and available in all LTS versions unless I'm missing something - are we talking about Channel or TracingChannel? If the former, all versions...

> Does it need to be that way by the spec? it appears as though it shouldn't be async

I will close once I see a few more CIs

https://github.com/nodejs/undici/actions/runs/6229473169/job/16908037511?pr=2272#step:14:10764 it's still happening

> make a FAQ about node-fetch vs fetch (undici) how users can get feature parity. Would you like to send in a PR? Please remember that the maintainers are people...