The Fetch Standard allows users to skip consuming the response body by relying on garbage collection to release connection resources. Undici does not do the same. Therefore, it is important to always either consume or cancel the response body.
This ended up causing a memory leak because I was relying on this without realizing when determining whether or not a Remix Resource's creator has a GitHub Sponsors page setup.
Undici does not garbage collect unconsumed response bodies
This ended up causing a memory leak because I was relying on this without realizing when determining whether or not a Remix Resource's creator has a GitHub Sponsors page setup.