Skip to content
Source
Sign inSign up
TanStack/db

Disabled useLiveQuery fails SSR hydration with error 253 #2322

Send to my agent
OpenJaime02(GitHub profile, opens in a new tab) opened this issue 0 comments
  • I've validated the bug against the latest version of DB packages (main at 15d2d2d32)

Describe the bug In a routerWithDbClient app, hydration fails when a live query is disabled, meaning its query callback returns undefined:

TanStack DB error 253 (The DB stream ended before the server-rendered query snapshot arrived.)
    at DbClient._setSsrStreamingEnabled

React reports a hydration error (#422) and falls back to client rendering for the boundary. This happens in both dev and production builds.

Cause A disabled query has no collection, so the server never captures or streams a record for it. LiveQueryObserverClient.getServerSnapshot still calls _waitForSsrLiveQuery(queryHash, true) for its hash. While the DB stream is open, the hydration read suspends. When the stream ends, it throws 253.

To Reproduce In examples/react/start-ssr-e2e, add a route:

function DisabledQueryRoute() {
  const [id] = React.useState<string | undefined>(undefined)
  const { status } = useLiveQuery({
    query: (q) => (id === undefined ? undefined : q.from({ todo: ssrTodoCollection })),
  })
  return <span>{status}</span>
}

Load the route with vite build && vite preview or with vite dev. The error event's cause chain contains error 253.

Expected behavior A disabled query hydrates as status: 'disabled'. It should not wait for a record that the server never sends.

Additional context Versions: @tanstack/db / @tanstack/react-db 1.0.0-rc.1.1, @tanstack/react-router-with-db 1.0.0-rc.1, React 19, Chromium.

Sign in to join this conversation.