Server-Side Rendering and Live Queries
TanStack Start routes render on the server for the first pageload of a browsing session. Neither the React Query nor standard Convex useQuery()
hooks kick off requests for this data during this initial SSR pass, but the React Query hook useSuspenseQuery()
does. The React Query client is then serialized with whatever data was loaded to make it available in the browser at hydration time. This reduces rendering on the server and updating on the client from two steps to one step: isomorphic data fetching with a single hook.
Try reloading this page to see the difference between useSuspenseQuery()
and useQuery()
.
hi Jamie- how was your weekend?
hey Emma, how's the weather in SF?
hey Nipunn- how was your weekend?
Hi Nipunn; how was your weekend?
hi Nipunn, I'll be late to make the meeting tomorrow morning
Hi Jamie; how's the weather in SF?
hey Jamie... how's the weather in SF?
hey Emma- what's your favorite ice cream place?
Hi Nipunn! Could you let the customer know we've fixed their issue?
hi Jamie... how was your weekend?
hello Emma, I'll be late to make the meeting tomorrow morning
hi Nipunn- how was your weekend?
hey Jamie! what's your favorite ice cream place?
hello Emma! how was your weekend?
Hi Jamie! Could you let the customer know we've fixed their issue?
hello Jamie; how's the weather in SF?
hi James! I'll be late to make the meeting tomorrow morning
hi Jamie! how's the weather in SF?
hello Nipunn, Could you let the customer know we've fixed their issue?
hey James; what's your favorite ice cream place?
1const { data } = useSuspenseQuery(convexQuery(2 api.messages.listMessages,3 { channel: "chatty" }4))
1const { data, isPending } = useQuery(convexQuery(2 api.messages.listMessages,3 { channel: "chatty" }4))
On the browser these queries resume their subscriptions which you can see by .
Another way to opt into server-side data loading is to load the query in a loader.