Khafra

Will be fixed by #1697 ~~https://github.com/web-platform-tests/wpt/blob/master/fetch/api/response/response-clone.any.js~~ ~~These tests are mostly/all failing due to us not cloning the tee'd ReadableStream from response.clone()~~ ~~A fix would look like:~~ ```js const [out1, out2]...

Another test fails due to fetch allowing binding of `this`: Expected outcomes: ``` const url = 'https://example.com' await fetch.call({}, url) // rejects await fetch.call(undefined, url) // resolves await fetch.call(globalThis, url)...

I will experiment with it, but none of my initial attempts got anywhere

> > > It's that easy? wow... It should be, hopefully :)

Sounds good, although both [Web streams](https://nodejs.org/dist/latest-v16.x/docs/api/webstreams.html#webstreams_web_streams_api) and [Blob](https://nodejs.org/dist/latest-v16.x/docs/api/buffer.html#buffer_class_blob) are both considered experimental currently which is causing the holdup to the discordjs pr.

any idea how to fix the merge conflicts? they're not showing on my side, only here

Okay should be relatively good, still not familiar with yarn so I don't really know where the types change occurred (and I'm a little lazy) Also I committed these changes...

Spreading into an empty object does a shallow clone. However, undici's `Dispatcher.ResponseData` (res) has a private symbol property that exposes the underlying stream, which is probably causing the same issue....

commented out, unchanged from install

ws is great but I think the implementation is *too different* from the spec WebSocket. There's also outstanding issues where it uses a custom EventTarget (https://github.com/websockets/ws/issues/1818). Then there's a bunch...