TanStack
OSS
router
Sign in / Sign up
Open main menu
router
GitHub
Overview
Runs
Analytics
Loading workspace stats
Loading workspace insights...
Statistics interval
7 days
30 days
Latest CI Pipeline Executions
Status
Fix filter
Filter
Fuzzy
Filter range
Sort by
Sort by
Start time
Sort ascending
Sort descending
Succeeded
7734
85f092a7 chore: add changeset for defaultNotFoundComponent hydration fix
by Brenley Dueck
B
Succeeded
7734
3f32ef5b fix(solid-router): resolve defaultNotFoundComponent at render time to avoid hydration desync Previously defaultNotFoundComponent was applied by lazily mutating the boundary route's options.notFoundComponent when a notFound was handled. Route objects are module singletons shared across server requests, so once the server handled any 404, later SSRs of valid URLs wrapped the match in a CatchNotFound boundary the freshly-hydrating client doesn't render, shifting hydration keys and leaving the subtree unclaimed (visible but inert DOM). Resolve defaultNotFoundComponent at render time in Match.tsx so the boundary structure is deterministic on both server and client, and add an e2e regression test.
by Brenley Dueck
B
Canceled
7734
3f32ef5b fix(solid-router): resolve defaultNotFoundComponent at render time to avoid hydration desync Previously defaultNotFoundComponent was applied by lazily mutating the boundary route's options.notFoundComponent when a notFound was handled. Route objects are module singletons shared across server requests, so once the server handled any 404, later SSRs of valid URLs wrapped the match in a CatchNotFound boundary the freshly-hydrating client doesn't render, shifting hydration keys and leaving the subtree unclaimed (visible but inert DOM). Resolve defaultNotFoundComponent at render time in Match.tsx so the boundary structure is deterministic on both server and client, and add an e2e regression test.
by Brenley Dueck
B
Previous page
Previous
Next
Next page