Next.js: Unified Request Traces and Streaming Cache Fix
Request observability was unified so middleware, render and instrumentation now share one trace, while streaming cache revalidation was fixed to flush at response close. Turbo Tasks and Turbopack also gained batched invalidation and true code-splitting for lazy matches.
Duration: PT2M35S
Episode overview
This episode is a short developer briefing from Next.js.
It explains recent repository work in plain language.
- Show: Next.js
- Published: 2026-10-22T13:15:20Z
- Audio duration: PT2M35S
Transcript excerpt
This excerpt keeps the crawler page concise. Listen to the episode or use the RSS feed for the full update.
Good morning, it's Thursday, October 22nd, 2026, and this is your Next.js daily briefing.
The lead story is reliability in two places: request traces finally stay together, and cache work queued during streaming no longer gets dropped.
First, observability. A five-part stack from Tobias Koppers reworks Open Telemetry so each request produces one connected tree. Pull request 100349 starts the request span before route module preparation, eliminating parentless preparation traces on direct entry points. Pull request 100294 then makes middleware and…
Second, streaming cache correctness. Pull request 100448 fixes revalidation queued during streaming. Previously, Next.js flushed after preparing the HTML stream or running a Route Handler, before the body finished. Anything queued mid-stream missed wait-until coverage and tag invalidations were never dispatched. Now…
Third, build engine performance. Pull request 100485 adds batched invalidation, with related work in 100437 and 100465 to unemit collectibles and restore tasks in single operations — cutting evicted fan-out time by about twenty percent in benchmarks. On the Turbopack side, pull request 100522 fixes lazy import meta…
What's…
Nearby episodes from Next.js
- Build Scale Wins and Cache Reliability Fixes
- Turbopack Chunking Overhaul Lands
- Faster Flight Rendering and Tracing Fixes
- Reliability Fixes, Cache Tests, and Leaner Traces
- Cache Correctness and Turbopack Throughput
- Rendering Decoupled, Streaming Cache Fixes
- Turbopack Correctness, Leaner Proxy, and Flake Fixes
- Stale Cache Fixes and Missing Routes