Prerender HTTP access fallbacks with Cache Components semantics#93988
Merged
Conversation
Contributor
Author
This stack of pull requests is managed by Graphite. Learn more about stacking. |
Contributor
Tests PassedCommit: a228fb3 |
unstubbable
force-pushed
the
hl/not-found-cache-components-test
branch
from
fe2b093 to
c5f107f
Compare
unstubbable
force-pushed
the
hl/not-found-prerender-cache-components
branch
2 times, most recently
from
2953ec5 to
0321455
Compare
gnoff
approved these changes
May 20, 2026
The body of `if (cacheComponents)` in `prerenderToStream` is extracted into a local helper, `prerenderWithCacheComponents(getPayload)`. The catch-block error paths now route through that helper whenever Cache Components is enabled, which means the legacy `prerender-legacy` store is no longer reachable from a Cache Components prerender. As a result, `notFound()`, `forbidden()`, and `unauthorized()` recovery renders the matching fallback boundary under `prerender` and `prerender-client` semantics. Dynamic API access in those boundaries — for example `useSearchParams()` without a surrounding `<Suspense>` — now surfaces as a blocking-route error instead of the legacy `BailoutToCSRError`.
unstubbable
force-pushed
the
hl/not-found-prerender-cache-components
branch
from
0321455 to
a228fb3
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.
The body of
if (cacheComponents)inprerenderToStreamis extracted into a local helper,prerenderWithCacheComponents(getPayload). The catch-block error paths now route through that helper whenever Cache Components is enabled, which means the legacyprerender-legacystore is no longer reachable from a Cache Components prerender.As a result,
notFound(),forbidden(), andunauthorized()recovery renders the matching fallback boundary underprerenderandprerender-clientsemantics. Dynamic API access in those boundaries — for exampleuseSearchParams()without a surrounding<Suspense>— now surfaces as a blocking-route error instead of the legacyBailoutToCSRError.The dev side will be handled in a follow-up. The prerender handling diverged a bit from the dev rendering in #92231, and we'll likely need to re-align the dev rendering first.
Tip
Best reviewed with hidden whitespace changes.