Khafra
Khafra
they were, but it caused flakiness in the CI.
no, it was a while ago. It also wasn't at once: - all WPTs were run in separate workers (CI was flaky) - so then I limited it to 10...
this is already possible with CacheStorage, it's just not automatic (and it *is* an in-memory cache right now). adapted from mdn: ```js import { caches, Request, fetch } from 'undici'...
I don't think automatic caching is a good idea, it's possible via the dispatcher API in a way that is extendable and configurable (you can use whatever storage method you...
We are spec compliant, caching is completely optional. `httpCache` can be null and therefore caching is ignored: > If httpCache is null, then set httpRequest’s [cache mode](https://fetch.spec.whatwg.org/#concept-request-cache-mode) to "no-store". I...
yeah, that's what I had in mind. Rather than undici implementing it, provide some interface that other caching libraries can use instead.
I'll update the test actually, to use fs.openAsBlob instead.
cc @nodejs/llhttp
Without consuming the body I couldn't get node to gc the Response returned from fetch
no luck with that either, there are quite a few things that also have strong references to them (requestObject, controller, etc.). It'd be pretty messy dealing with all of them....