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- I'll be late to make the meeting tomorrow morning
hi Nipunn, what's your favorite ice cream place?
hi Jamie- how was your weekend?
hello James, what's your favorite ice cream place?
hey Nipunn- what's your favorite ice cream place?
hey James; how's the weather in SF?
Hi Emma- how was your weekend?
hi Emma, Could you let the customer know we've fixed their issue?
hey James; Could you let the customer know we've fixed their issue?
Hi James- how was your weekend?
hi Jamie- what's your favorite ice cream place?
hi James; what's your favorite ice cream place?
hi Nipunn... I'll be late to make the meeting tomorrow morning
hello James... Could you let the customer know we've fixed their issue?
hi Jamie; I'll be late to make the meeting tomorrow morning
hello James; I'll be late to make the meeting tomorrow morning
hello Jamie! how was your weekend?
hi Nipunn- what's your favorite ice cream place?
hello James! what's your favorite ice cream place?
hey James... how was your weekend?
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.