Khafra

> Why? To save time for undici developers, as they now did not need to import it via npm install? No. Fetch was added because it was one of --...

https://github.com/nodejs/undici/blob/c83b084879fa0bb8e0469d31ec61428ac68160d5/docs/api/Dispatcher.md?plain=1#L214 it would appear as though either the docs are wrong or the code should work without an onBodySent, not entirely sure which is more correct.

Needs benchmarks but probably slower in some areas, same in others. Busboy uses streamsearch (which implements a Boyer-Moore-Horspool algorithm) to search for boundaries after bodies etc. While this implementation is...

> I asked if we could at least add content-length to each and every field. I was actually wondering why there wasn't a content-length header -- it's a really poor...

I'm much more interested in replacing the asynchronous parsing with a synchronous parser. Not only is it actually spec compliant, but it will finally cleanup the body consumers. It doesn't...

This doesn't seem to be an issue with Deno/bun (or any of the browsers, although their use case is different). Since `request.body` is a ReadableStream, we could document formData's downsides...

There's also the issue of *how* parsing a multipart/form-data should be parsed and there's no actual spec for it. The WPT coverage sucks as well, while it's really good for...

I agree that we probably won't find middle ground for this 😄. > it should just work as it's intended to work. That's partially the issue - it doesn't work...

It's mostly done, just need to spent a couple hours adding docs and cleaning stuff up. Is there a way to opt-in to using the file backed Blobs, or is...

yes, the parsing should be done synchronously to match the spec.