Khafra
Khafra
```js const { fetch } = require('./index.js') async function run () { await fetch('https://example.com') } run() // otherwise process will end setTimeout(() => {}, 120000) ```
I don't understand. You can already write new code that is incompatible between browsers and node.js by using the returned Timeout object. I see plenty of new code use .unref()...
I think we are steering away from the topic - if there are no plans of deprecating or changing the return type, then I don't really see the justification for...
I'd like to drop FileLike and FileReader too.
this looks similar to https://github.com/nodejs/undici/commit/fdeccc23b510bda706f5b62921a72ecdc593bda4
``` node -p "`node: ${process.version}, undici: ${process.versions.undici}`" node: v22.15.0, undici: 6.21.2 ``` It seems like the commit didn't make it into the v6.21.2 release https://github.com/nodejs/undici/pull/4210
How is this different from https://github.com/nodejs/undici?tab=readme-ov-file#specification-compliance and https://github.com/nodejs/undici?tab=readme-ov-file#requestbody ?
I am able to reliably repro it when fetching too many urls at once. https://github.com/nodejs/node-core-utils/issues/810
If receiving an array is expected, #4390 is fine. If it isn't, I think it'd be more beneficial to align the dispatcher header behavior (in general, since it seems like...
Would it make more sense for undici to always overwrite the global dispatcher (if it's not from undici already)? Importing `node:http` might not cause issues anymore, but you'd still have...