Next.js: Router Reliability Gets a Deep Cleanup

A cluster of navigation and Server Action bugs tracing back to earlier router rewrites got fixed this cycle, alongside a "use cache" correctness pass and a bundle-size cleanup that automates browser-only module detection.

Duration: PT2M41S

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-07-03T14:22:59Z
  • Audio duration: PT2M41S

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 your Next.js briefing for July 3rd, 2026.

The clearest thread today is the router settling down after a run of regressions in recent releases. Three separate fixes from Dan Abramov all trace back to how navigation state and Server Actions interact. PR 95391 fixes navigation spuriously reverting when a Server Action is still in flight — a regression from a…

Second theme: "use cache" correctness. Hendrik Liebau landed three related fixes — a false-positive nested-cache error when someone overrides the default cache-life profile with a short expiration, a change to skip writing `expire: 0` values to the default cache handler in production since they're never served back,…

Third, a maintenance push on bundle size: Sebastian Silbermann's pair of PRs, 95200 and 95201, replace a hardcoded list of browser-only module variants with automatic detection plus a lint rule, closing off a class of bundle-size regressions.

Also worth noting: React was upgraded to a fresh snapshot, and a source-map fix now correctly ignore-lists internal frames whose maps chain back to original source files, cleaning up noisy stack traces in dev.

What's next: if you're on a recent canary and…

Nearby episodes from Next.js

  1. Root Params and Performance Infrastructure
  2. Weekly Recap - API Stabilization & Dev Experience
  3. Memory Optimization and Streaming Fixes
  4. Router Instrumentation and Performance Optimizations
  5. Cache Components and Turbopack Infrastructure Improvements
  6. Cache Components Stabilization and Developer Experience Improvements
  7. API Stabilization and Developer Experience
  8. Runtime Optimization and API Stabilization