Surface an error for blocking routes under the Navigation Inspector#95139
Merged
Conversation
Contributor
Tests PassedCommit: 678bae5 |
Contributor
Stats cancelledCommit: 678bae5 |
samselikoff
approved these changes
Jun 24, 2026
When the Navigation Inspector (Instant Navigation Testing API) is active, the server renders only a route's static shell. A blocking route — one that reads a dynamic value such as `await cookies()` at the root with no Suspense boundary above it, opting into blocking via `export const instant = false` — produces an empty shell. We served that empty shell directly, so the browser showed a blank document with no DevTools. With no DevTools, there's no way to release the inspector lock from the UI, so every reload stayed blank and the user was stuck. Detect the empty static shell at serve time and throw to surface a normal error page instead, and clear the instant-navigation cookie so the next reload renders the route normally. In the future we plan to render this error message inline in the Navigation Inspector panel rather than as a full-page error.
acdlite
force-pushed
the
acdlite/instant-nav-blocking-route-error
branch
from
3bce27d to
678bae5
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
When the Navigation Inspector (Instant Navigation Testing API) is active, the server renders only a route's static shell. A blocking route — one that reads a dynamic value such as
await cookies()at the root with no Suspense boundary above it, opting into blocking viaexport const instant = false— produces an empty shell. We served that empty shell directly, so the browser showed a blank document with no DevTools. With no DevTools, there's no way to release the inspector lock from the UI, so every reload stayed blank and the user was stuck.Detect the empty static shell at serve time and throw to surface a normal error page instead, and clear the instant-navigation cookie so the next reload renders the route normally.
In the future we plan to render this error message inline in the Navigation Inspector panel rather than as a full-page error.