Next.js: Client Navigation Edge Cases, Squashed

One contributor, QuarkOS, shipped five separate fixes for client-side navigation and rendering edge cases involving redirects, caching, and streaming, while a parallel effort tightened Turbopack's concurrency internals for large builds.

Duration: PT3M14S

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-08-31T13:12:48Z
  • Audio duration: PT3M14S

Transcript excerpt

This excerpt keeps the crawler page concise. Listen to the episode or use the RSS feed for the full update.

Good day, and welcome to Next.js briefing for August 31st, 2026.

Today's biggest signal isn't one headline fix — it's a cluster of five separate navigation bugs, all fixed by the same contributor, all involving state that gets stuck between client and server.

Start with cache components. PR 98088 fixes a case where clicking a link into a fully dynamic route that calls redirect never actually navigated — it just spun. PR 98087 fixes a related problem: a stalled RSC request could poison the back-forward cache, so later clicks on that route silently did nothing until the…

Second theme: cache handler correctness. PR 98039, paired with commit 00b2275, rewrites the documented contract for custom cache handlers after discovering the example code itself could lock a stream and crash a page. PR 98098 and 98049 followed up by making test cache handlers actually forward expiration and soft…

Third theme: Turbopack scaling. PR 98093 shards a single lock that was reportedly blocking over half of thread time on a 166-thread build. PR 98090 replaces a task storage map with dense, chunked storage for better memory locality. And PR 98091 removes an unnecessary caching boundary called 223,000 times…

Also…

Nearby episodes from Next.js

  1. Weekly Recap - Turbopack Hardening and Cache Correctness
  2. Closing the Gaps Between Client and Server Truth
  3. Prerender Correctness and a Repo Cleanup Sweep
  4. Turbopack Trims Bundles While Router Fixes Correctness
  5. Image Pipeline Stability and Turbopack Deadlock Fixes
  6. Turbopack's Push Toward WebAssembly
  7. WebAssembly Cleanup and Cache Correctness Fixes
  8. Cutting the Route Table Down to Size