Next.js: Go Front Server and Leaner Production Builds
Next.js merged an experimental Go front server for next start and a set of Turbopack build efficiency changes. The broader pattern is lower memory, smaller output, and more reliable routing and tests.
Duration: PT2M39S
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-11-19T14:11:24Z
- Audio duration: PT2M39S
Transcript excerpt
This excerpt keeps the crawler page concise. Listen to the episode or use the RSS feed for the full update.
Hello, it's Thursday, November 19th, 2026, and this is your Next.js daily briefing.
The lead story is a long-term bet on production performance. Next.js is introducing an experimental Go front server in front of next start, while simultaneously cutting build memory, chunk size, and duplicate output.
First, the front server. In PR 101695, merged November 19th, an opt-in Go program takes ownership of the public port and forwards every request unchanged to the existing Node server on a private loopback port. It makes no routing decisions yet. The goal is to establish an HTTP front that can take over routing work…
Second, leaner builds. PR 102061 proposes an opt-in build worker that runs Turbopack compilation in a dedicated child process, aimed at large apps where the main build holds around 12 gigabytes of peak memory. That pairs with PR 100478, now merged, which adds a best-effort upper bound on JavaScript chunk size, with…
Third, routing reliability. Two fixes address a Pages Router hang when navigation joins a prefetch that later fails or times out, in PRs 102043 and 102051. Related App Router fixes preserve empty static shell allowance during fallback regeneration with custom cache…
O…
Nearby episodes from Next.js
- Turbopack Reliability Fixes and Switchyard Routing
- Rust Build Push and Worker Overhaul
- Turbopack Rework, Cache Safety and Test Groundwork
- Turbopack Warm Build Breakthrough
- Native Go Proxy and Build Hardening
- Weekly Recap - Engine Efficiency and Rendering Correctness
- Turbopack Reliability and Build Performance Push
- Cache Miss Fixes and Turbopack Slimdown