Run details

docs(chat): clarify fetcher vs stream is async-vs-sync, not Response-vs-iterable A `fetcher` can also return an `AsyncIterable<StreamChunk>` (sync or `Promise`-wrapped), not just a `Response` — the previous tip implied a clean Response/iterable split. The real distinction is that `stream()`'s factory must return the iterable *synchronously*, so an async server-function call (always a `Promise`) needs `fetcher` regardless of what it resolves to. Also corrects the pre-existing `stream()` section, which listed "TanStack Start server functions" as a `stream()` use case — those are async and hit the #509 type error; redirect them to `fetcher` and reframe `stream()` as the synchronous in-process / RSC / test path. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

nx run-many --targets=build --exclude=examples/**,testing/**

Succeeded

CI Pipeline Execution

4 CPU cores

6b495eb8681

100%

Cache hits

31 of 31 tasks used cache.

Get faster results

Learn how to enable distribution.

Atomizer enabled

31 groups of tasks optimized.

© 2026 - Nx Cloud

Terms of Service Privacy Policy Changelog Status Docs Contact Nx Cloud Pricing Company @NxDevTools