bug(fetch): Reponse.text() hangs if you've cloned the response

[Lioness100]

trafficstars

Is there an existing issue for this?

• [X] I have searched the existing issues

Description of the bug

Basically just https://github.com/node-fetch/node-fetch/issues/1131. The solutions that are offered are using highWaterMark, which might not be possible with cross-fetch, or "to resolve cloned response in parallel", which might not be applicable with cross-fetch? I don't know much about cross-fetch or the technicalities of fetching in general, so help would be appreciated.

Steps To Reproduce

See https://github.com/node-fetch/node-fetch/issues/1131

Expected behavior

See https://github.com/node-fetch/node-fetch/issues/1131

Screenshots

No response

Additional context

No response

[kyranet]

Considering we don't use node-fetch but rather globalThis.fetch, which is undici powered, is this issue still relevant today?