Next.js: Developer Experience and Turbopack Improvements

Transcript

Good morning. This is your Next.js developer briefing for May 19th, 2026.

The team merged 13 pull requests yesterday, with significant improvements to developer tooling and bug fixes. Mischnic merged a major Turbopack update switching from base40 to base38 hash encoding, affecting 546 files across the codebase. This change addresses issues with hash collisions and improves build reliability.

Aurora Scharff enhanced the instant error overlay to better distinguish between navigation errors and initial render errors. The overlay now clears navigation-specific warnings when users change routes, preventing error accumulation and providing more contextual feedback during development.

Several important backports were merged by Unstubbable, including fixes for hydration failures when pages are served from HTTP cache, proper encoding of non-ASCII characters in cache tags, and resolution of server action forwarding loops with middleware rewrites. A routing fix addresses catch-all router.query corruption when using basePath with rewrites.

Luke Sandberg improved error handling in Next.js configuration by moving config evaluation inside try-catch blocks, ensuring developers see appropriate help links when export functions throw errors.

The team also split the og-api test suite into default and standalone variants to prevent build crashes in certain deployment scenarios, and updated adapter APIs to pass project directory information to the modifyConfig function.

What's next: These changes improve development experience with better error messaging and resolve several edge cases in caching and routing. The Turbopack encoding update should provide more reliable builds across different environments.

That's your Next.js update. Back tomorrow with more developments.