Next Js Daily: Chasing Down Tracing and Runtime Regressions
Today's activity centers on cleanup after recent architectural shifts in Turbopack and Cache Components, with two production-affecting regressions fixed and a major runtime bootstrap refactor landing as a completed stack. Developers on cache components or standalone deployments should pay close attention.
Duration: PT2M41S
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-07-16T22:00:28Z
- Audio duration: PT2M41S
Transcript excerpt
This excerpt keeps the crawler page concise. Listen to the episode or use the RSS feed for the full update.
It's July 16th, 2026, and this is Next Js Daily.
The clearest thread today: teams are paying down risk from recent refactors, catching regressions before they bite harder in production.
Start with tracing. PR 95824, from gaearon, fixes a real deploy-breaking bug: the recent NFT rewrite behind PR 95815 only traced the RSC template's module graph, not the separate graph used by server actions. That meant packages imported only from a server action could end up as broken symlinks in standalone output,…
Second regression thread: Cache Components. PR 95853 reverts a same-document navigation change from PR 95682 after it broke CC navigation, and gaearon is following up by expanding CC test coverage in PRs 95877 and 95878, specifically calling out that the navigation suite had been running with CC disabled. That's a…
Related: acdlite's PR 95415 unifies the experimental app-shells flag into Partial Prefetching, meaning shell optimizations that were purely internal now ship without a gate, while behaviors that change request counts stay tied to Partial Prefetching opt-in. Net effect: no prefetch cost regression unless you've…
Third theme: the Turbopack runtime bootstrap stack from sampoder —…