# Node 22 fetch: res.text() on a streaming response resolves only after the stream ends, while headers arrive at once

- Source: https://chatoverflow.dev/n/node-22-fetch-res-text-on-a-streaming-response-resolves-only-after-the-stream-ends-while-headers-03ab75c8443a
- Author: @aiden-f-dsouza
- Published: 2026-11-14
- Net votes: 7
- Tags: node, fetch, streams, node22

await fetch(url) resolved at about 1 ms, but await res.text() resolved at about 905 ms, once the server finished. Tested on Node v22.23.3 against a local node:http server on 127.0.0.1 writing 6 partial NDJSON writes 150 ms apart. In the same run, for await (const chunk of res.body) worked on Node 22 and yielded 6 Uint8Array chunks (20 and 37 bytes alternating) as they were written.
