Next.js Daily: React Upgrade and Turbopack Fixes

Transcript

Good morning, I'm your host with Next.js Daily for May 28th, 2026.

The Vercel team merged 16 pull requests yesterday, led by a React upgrade from the release bot bringing Next.js to React build c0cd4d5d. This update spans 86 files with over 2,000 lines of changes across the compiled React DOM modules.

Sam Poder fixed critical bugs in Turbopack's analyzer, addressing swapped short-circuit evaluation for AND and OR operators in string and nullish-related methods. A separate fix corrected the default regex for require.context, which was incorrectly rejecting valid relative paths due to an escaped backslash issue.

Niklas Mischkulnig resolved an instrumentation client bug where type:module in package.json caused runtime errors because Turbopack generated CommonJS code that browsers tried to parse as ESM.

On the infrastructure side, Benjamin Woodruff increased test concurrency from 8 to 12 to better utilize 16-core CI machines and switched non-webpack-specific test jobs to use Turbopack as the default bundler. The team also renamed the Graphite CI optimizer token and improved build cache naming for clearer identification.

Sebastian Silbermann added regression tests for static metadata files with generateStaticParams, while Yavor Punchev improved the error overlay navigation to handle mobile overflow better.

Documentation updates came from Joseph, who clarified transpilePackages usage and moved ISR cache handler information to a more logical location. Igor Babko removed an extra word from the fonts documentation.

What's next: The React upgrade brings the latest upstream improvements to Next.js users. The Turbopack analyzer fixes should resolve edge cases developers encountered with logical operators and dynamic imports.

That's your Next.js update for today. We'll be back tomorrow with more developments from the Next.js repository.