Next.js: Dev Server Stability and the Great Websocket Reconnect Fix
A cluster of fixes this cycle target development server reliability — from Rspack crashes and HMR reconnect loops to duplicate type declarations — alongside a quieter push to close gaps in prerendering correctness for cached pages and static variants.
Duration: PT2M54S
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-09-04T13:12:12Z
- Audio duration: PT2M54S
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 September 4th, 2026.
The clear throughline today is developer-facing stability: multiple independent bugs converged on the same failure mode — the dev server getting stuck, crashing, or reconnecting endlessly — and the team closed them out within a tight window.
Start with hot module reload. Two separate pull requests, 98229 and 98227, fixed the same root cause: the dev websocket client was reconnecting whenever the socket wasn't fully open, not just when it was closed. That meant a socket still in the process of connecting — commonly triggered by Chrome's speculation-rules…
Alongside that, PR 98228 fixes a Rust panic in Rspack dev builds when the error overlay tries to source-map a stack frame mid-rebuild — another case of the dev server tripping over its own concurrency. And PR 98244 stops a spurious webpack rebuild loop on cold start when Tailwind references content directories that…
Second theme: prerendering correctness for cached and static content. PR 98255 completes a fix started earlier so that dynamic parameter access is tracked consistently between prospective and final prerenders — closing a gap where hanging params could…
Small…
Nearby episodes from Next.js
- Cleaning Up the Test Harness and Trimming Turbopack's Footprint
- Turbopack Memory Overhaul and the Great Test Gate Migration
- Hardening Cache, HMR, and Error Responses
- Client Navigation Edge Cases, Squashed
- Weekly Recap - Turbopack Hardening and Cache Correctness
- Closing the Gaps Between Client and Server Truth
- Prerender Correctness and a Repo Cleanup Sweep
- Turbopack Trims Bundles While Router Fixes Correctness