ssr:false: redirect thrown in a child beforeLoad during the initial load blanks the app (MatchInner throws `undefined`), reproducer for #7910 #8783
Send to my agentVersions:
- @tanstack/react-router 1.170.18
- @tanstack/router-core 1.171.15
- @tanstack/react-start 1.167.x (start-client-core 1.170.14)
- React 19.2
- Vite 8.1, dev mode
Describe the bug#
A full page load of a URL under an ssr: false layout, where a child route's async beforeLoad throws redirect(), can leave the page blank. The console shows Uncaught undefined and "An error occurred in the component".
Navigating to the same URL client-side works.
This is the issue reported in #7910, which was closed for lack of a reproducer. Here is one with no .preload() forwarding.
Minimal reproduction#
// routes/zzrepro.tsx
export const Route = createFileRoute("/zzrepro")({
ssr: false,
beforeLoad: async () => { await wait(200); return { user: { id: "x" } } },
component: () => <Outlet />,
})
// routes/zzrepro.a.tsx
export const Route = createFileRoute("/zzrepro/a")({
beforeLoad: async () => { await wait(200); throw redirect({ to: "/zzrepro/b" }) },
component: () => <div>A</div>,
})
// routes/zzrepro.b.tsx
export const Route = createFileRoute("/zzrepro/b")({
beforeLoad: async () => { await wait(200) },
component: () => <div>B rendered OK</div>,
})
In our app, the redirect alone was enough to blank the page.
In this synthetic version it reproduces deterministically if router.invalidate() is also called while the redirected load is in flight, about 500–900 ms after page load.
For example, Supabase's onAuthStateChange emits SIGNED_IN on every page load. A root-level listener that calls router.invalidate() on it hits this window.
Analysis#
- The
ssr: falsematch is dehydrated aspending. On the client,hydrate()puts it in the active matches, androuter.load()runs the guards. - The child throws a redirect.
navigate({ replace: true })starts a new load whose pending matches reuse the same id for thessr: falselayout. They share_nonReactive. - That load finishes the layout match.
loadRouteMatchresolves and clears_nonReactive.loadPromise. This happens beforeonReadycommits the pending matches. - React renders the still-active stale snapshot (
status: "pending").MatchInnerImpldoesthrow getMatchPromise(match, "loadPromise"), which isundefined. CatchBoundarystoresundefinedas the error. That is falsy, so it re-renders its children, which throw again. React gives up and unmounts the root.- The router state afterwards is correct (all matches
success), but nothing is mounted.router.state.statusstayspendingforever.
Workaround we ship (patch-package)#
In MatchInnerImpl's getMatchPromise:
return router.getMatch(match.id)?._nonReactive[key]
?? match._nonReactive[key]
?? router.latestLoadPromise
?? new Promise((resolve) => setTimeout(resolve, 0))
Suggested fixes#
- Never throw a non-thenable from the pending branches.
- Or keep
loadPromisealive until the pending matches are committed. - Separately,
CatchBoundarycould treat a thrownundefinedas an error, so it renders theerrorComponentinstead of looping.
Sign in to join this conversation.
we always need complete projects as reproducer