Next.js Daily: Turbopack Goes Wasm-Ready

A large coordinated stack from Tobias Koppers ported Turbopack's core toolchain to compile and run on wasm targets, while separate fixes tightened Turbopack's path resolution and symlink handling for correctness and security.

Duration: PT2M17S

Episode overview

This episode is a short developer briefing from Next.js Daily.

It explains recent repository work in plain language.

  • Show: Next.js Daily
  • Published: 2026-08-26T06:06:46Z
  • Audio duration: PT2M17S

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 26th, and today's codebase activity centers on one big push: getting Turbopack running on wasm.

Roughly a dozen PRs from Tobias Koppers systematically removed compile blockers for wasm targets — event listener waiting, symlink creation through the WASI API, disabling the process pool and SWC's plugin host on wasm, and swapping crossterm for owo-colors to drop a problematic dependency. Several of these, like PR…

Second theme: path resolution correctness. PR ninety-seven seven ninety-nine fixes how slash-rooted imports resolve — previously they reached the filesystem root, which could escape a project directory entirely in a monorepo. Now they're pinned to the project directory, matching Vite's behavior. Related, PR…

Two more items worth flagging. Commit e8ed one forty-four adds parent-count reference counting to the turbo-tasks backend, letting it detect unreachable tasks without a database scan — a meaningful internal performance and correctness building block. And on the docs side, PR ninety-seven eight twenty-three and the…

What's next: watch for the remaining wasm-stack PRs, including the turbo-persistence mmap opt-out series, and the still-open…

Nearby episodes from Next.js Daily

  1. Fixing the Routing Table Under the Hood
  2. Weekly Recap - Trimming the Route Table and Taming Development Caching
  3. Binary Diets and Repo Spring Cleaning
  4. Tightening Up Dynamic Routing
  5. Prefetching Precision and Turbopack's Deep Cleanup
  6. Cleaning Up Native Test Dependencies, and Module Federation Lands on Turbopack
  7. Cleaning Up Test Debt and Prefetch Bugs
  8. Development Caching Gets a Rewrite