Next Js Daily: Navigation Reliability Under the Microscope
Andrew Clark landed two fixes for stuck and misreported client-side navigations tied to the Navigation Testing Lock, while a canary test-suite revert and Turbopack performance work rounded out a day focused on stabilizing the app router's core navigation model.
Duration: PT2M23S
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-17T22:00:37Z
- Audio duration: PT2M23S
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 July 17th, and this is Next Js Daily.
Today's biggest signal is instability in client-side navigation, surfaced and fixed by the same engineer, across two related pull requests.
Andrew Clark shipped PR ninety-five eight sixty-four, fixing repeated navigations that could get stuck when the Instant Navigation lock is held. The root cause: React's use deferred value hook doesn't behave the same way when updating a shared layout as it does when mounting new UI, so cached screens were sometimes…
Alongside that, Dan Abramov reverted PR ninety-five eight seventy-eight, which had expanded test coverage under the cache components flag, after it caused unexplained canary failures. That's a defensive move to protect the main branch while the root cause gets investigated.
The other theme is Turbopack performance. Two PRs from Marcos Hernanz, ninety-five nine oh three and ninety-five nine oh two, both target overhead reduction — reusing workers instead of respawning them, skipping unnecessary bookkeeping for cached roots, and adding a lightweight file watcher to cut hot reload latency…
Smaller but notable: a fix for confusing static paths error messages, error attribution…