Khafra

> The dispatch option is also not spec compliant I consider adding this to fetch/WebSocket a mistake. It should have been namespaced, like Cloudflare does with custom options. https://developers.cloudflare.com/workers/runtime-apis/request/#the-cf-property-requestinitcfproperties

That sounds great to me. I think it drastically reduces confusion and allows us to add whatever we want in the future, without having to regard conflicts with upcoming spec...

Yes but there seem to be related test failures

> So we have maybe some wiggle room and can define byte sequence matching that definition but have our own internal representation? Yes, this is something I struggled with before...

Where does the spec dictate that the description must be the error message? For example I'm pretty sure if we implemented URLMismatchError its message wouldn't be "Deprecated.".

Mostly being careful because this will break things, mostly tests https://github.com/search?q=%22This+operation+was+aborted%22&type=code

I'm not opposed to it, as long as it doesn't add an option to fetch

in the meantime, you can use Agent with fetch ```js import { fetch, Agent } from 'undici' const resp = await fetch('http://localhost/version', { dispatcher: new Agent({ connect: { socketPath: '/var/run/docker.sock'...

If we implement this we will deviate from literally every other platform. We should either let wintercg handle it, or let the spec handle it. -1

From a quick glance: 1. Bun allows fetching file:// urls with any method, Deno throws on non-GET calls. 2. Chrome only allows this for extensions, if users opt-in to it....