Next.js: Rust Build Push and Worker Overhaul

Turbopack moves route bundle stats and build metadata into Rust to cut build time, while Next.js replaces its Jest-based worker with a custom pool and compresses observability data. The examples catalog drops samples built on archived or sunset libraries.

Duration: PT2M26S

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-20T14:12:09Z
  • Audio duration: PT2M26S

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 Friday, November 20th, 2026, and this is your Next.js briefing.

The dominant pattern is performance through ownership: moving hot build paths out of JavaScript and into Rust and purpose-built infrastructure.

First, Turbopack now handles more of production output itself. In pull request 101540, route bundle statistics are computed in Rust and emitted as a normal build asset, removing a JavaScript step that loaded every page’s client manifest on the main thread. On a five-thousand-route test app, that cut about three…

Second, background work and observability got leaner. Pull request 100297 replaces the vendored Jest worker and its wrapper with a custom worker pool used by static generation, type checking, minification, and dev validation. Workers now spawn on demand with throttled boot, hung workers are replaced individually…

Third, the examples catalog is getting honest. Under new inclusion criteria, pull requests 102092 and 100454 remove samples built on archived or sunset platforms — Stitches, Rematch, Realm Web, Grafbase and Xata among them — while moving the Redis sample to Upstash Redis and the forms sample to Neon.

What’s next: expect follow-ups on…

Nearby episodes from Next.js

  1. Turbopack Reliability Fixes and Switchyard Routing
  2. Go Front Server and Leaner Production Builds
  3. Turbopack Rework, Cache Safety and Test Groundwork
  4. Turbopack Warm Build Breakthrough
  5. Native Go Proxy and Build Hardening
  6. Weekly Recap - Engine Efficiency and Rendering Correctness
  7. Turbopack Reliability and Build Performance Push
  8. Cache Miss Fixes and Turbopack Slimdown