Next.js: Turbopack Rollbacks and WebSocket Route Handlers Take Shape
Two experimental Turbopack optimizations were reverted after breaking real-world modules, while a cluster of PRs from David Ilie laid down the lifecycle infrastructure for experimental WebSocket route handlers.
Duration: PT2M21S
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-10T13:10:33Z
- Audio duration: PT2M21S
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 August 10th, and today's Next.js activity has two clear stories: Turbopack pulling back on aggressive optimizations, and WebSocket support getting real infrastructure.
Start with the reverts. Hendrik Liebau shipped two of them today. PR ninety-seven-oh-oh-nine undoes the change that made Turbopack follow re-exports for side-effect-free async modules — it was throwing "module id not found" errors with next slash dynamic. PR ninety-seven-oh-eighteen reverts CJS tree shaking being on…
Second theme: WebSocket route handlers are becoming a real feature, not just a prototype. David Ilie opened four connected PRs today — ninety-seven-oh-twenty-six through ninety-seven-oh-thirty-one — covering bounded WebSocket transport primitives, coordinated server lifecycles across dev, start, and custom servers,…
Smaller but useful fixes: routing correctly handles hash fragments in redirect destinations and normalizes i18n domain comparisons when a port is configured, both from yogesh968. And a build crash from symlinked directories in output file tracing includes, filed by sokra, addresses a fatal Turbopack error affecting…
What's next: watch for the WebSocket PRs to merge as a set,…
Nearby episodes from Next.js
- Stabilizing 16.3 and Unifying the Router's Data Format
- Turbopack Internals Get a Deep Cleanup
- Request State Gets Untangled
- Routing Loops and the PPR Cleanup
- Weekly Recap - Turbopack Hardening and the Render Pipeline Split
- Closing the Gaps in Cache Components
- Server Actions Get Rerouted, Request Insights Takes Shape
- Rebuilding the Router's Data Format, and a New Observability Layer