Next.js: Turbopack Path Handling Gets a Real Fix

A cluster of Turbopack fixes closed out long-standing gaps in how relative paths and import.meta.glob patterns are resolved, while the team quietly retired legacy test infrastructure like node-fetch and tsec across dozens of files.

Duration: PT2M40S

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-09-10T13:14:20Z
  • Audio duration: PT2M40S

Transcript excerpt

This excerpt keeps the crawler page concise. Listen to the episode or use the RSS feed for the full update.

Good day, and welcome to the Next.js briefing for September 10th, 2026.

The clearest signal today: Turbopack's path-resolution logic got a serious, coordinated overhaul, closing bugs that only surfaced when independent changes collided.

Sokra's PR 96557 fixed import.meta.glob so it correctly resolves parent-directory and root-absolute patterns, instead of silently returning empty results or dropping exclusion patterns — the worst possible failure for something meant to exclude files. That work exposed a follow-on gap: relative paths used as module…

Second theme: infrastructure cleanup. Eps1lon led a multi-PR push to remove node-fetch across the test harness, fixtures, and scripts — PRs 98195, 98346, and commit 76a0bdb — since Node now ships fetch natively. Same author also removed the unenforced tsec linter in PR 98423 and cleaned up an orphaned CI action in…

Third, rendering correctness: gnoff's PR 97345 makes metadata resolve independently per parallel route slot, behind an experimental flag, so one slot's error can't corrupt another's document head. And a Server Component not-found fix, PR 98455, addresses a long-open SEO issue where crawlers saw blank pages instead…

Watch for…

Nearby episodes from Next.js

  1. Caching Correctness and Turbopack Hardening
  2. Hardening Partial Prerendering and the Build Pipeline
  3. Build Hangs and Rendering Correctness Fixes
  4. Weekly Recap - Turbopack Performance and Caching Reliability
  5. Correctness Fixes Across Dev Tools and Turbopack
  6. Redirects, Accessibility, and Prerender Consistency Fixes
  7. Dev Server Stability and the Great Websocket Reconnect Fix
  8. Cleaning Up the Test Harness and Trimming Turbopack's Footprint