Results 315 comments of Khafra

> The issue appears to be a deadlock between undici's Web Streams implementation and Windows named pipe buffering. If this is the case, this would be a node core issue....

I think the types are correct here. undici.fetch doesn't return a global response.

The issue afaict is that the DOM types replaced the old iterator(s) types with a "HeadersIterator". All we should need to do is implement something similar. Lmk if my understanding...

1. [No it isn't](https://w3c.github.io/FileAPI/#dfn-file). 2. They exist. `new Headers()[Symbol.iterator]().xyz`

```js (async () => { const rs = new ReadableStream({ start (c) { c.enqueue(new Uint8Array(1000)) c.close() } }) const [out1, out2] = rs.tee() await out1.cancel() })() ``` What Request.clone is...