Next.js: Native Go Proxy and Build Hardening
Experimental native Go proxy support landed, shifting proxy logic to a compiled worker for dev and production. Builds also got more resilient with fixes for stale dev types, dangling symlinks, and clearer bundler errors.
Duration: PT2M27S
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-16T14:12:29Z
- Audio duration: PT2M27S
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 Monday, November 16th, 2026, and this is your Next.js briefing.
The lead story is native execution moving beyond routes to proxies, alongside a concerted push to stop everyday filesystem and type-state issues from breaking builds.
First, proxies go native. In PR 101464, an experimental flag now enables Go proxies compiled by Turbopack into a native HTTP worker for both dev and start. This first version matches all paths and uses deployment defaults, with support for continuation, rewrites, redirects, header overrides, cookies, body replay,…
Second, builds get less brittle. PR 100612 fixes a painful stale-state bug where dev type output lingered after routes were moved or deleted, causing type checks and builds to fail until the folder was manually cleared — now type generation and build prune it when no dev server holds the lock. Two fixes from PRs…
Under the hood, Turbopack task work continues. PR 101734 batches cleanup of keyed dependency edges, cutting lock churn with multi-fold speedups in range-shift benchmarks, while PR 101766 standardizes collectible tracking on flat edge storage.
What's next: expect follow-ups for file-local Go proxy config, shared-runtime…
Nearby episodes from Next.js
- Rust Build Push and Worker Overhaul
- Go Front Server and Leaner Production Builds
- Turbopack Rework, Cache Safety and Test Groundwork
- Turbopack Warm Build Breakthrough
- Weekly Recap - Engine Efficiency and Rendering Correctness
- Turbopack Reliability and Build Performance Push
- Cache Miss Fixes and Turbopack Slimdown
- Turbopack Memory Cuts and Dev Reliability