Dehydrating/hydrating queryClient
How can i properly "hand off" the queryClient to the client, using TanStack Start with
Currently I don't do any hydration. This means I'm fetching data first on the server, then I throw it all away and fetch everything again on the client, completely negating any benefits of running the loader on the server.
I've read some docs:
https://tanstack.com/query/v5/docs/framework/react/guides/ssr
https://tanstack.com/query/v5/docs/framework/react/guides/advanced-ssr
and I see that with document SSR you can use
ssr: "data-only"Currently I don't do any hydration. This means I'm fetching data first on the server, then I throw it all away and fetch everything again on the client, completely negating any benefits of running the loader on the server.
I've read some docs:
https://tanstack.com/query/v5/docs/framework/react/guides/ssr
https://tanstack.com/query/v5/docs/framework/react/guides/advanced-ssr
and I see that with document SSR you can use
<HydrationBoundary>hydrate()dehydrate()await queryClient.prefetchQuery()In this guide you'll learn how to use React Query with server rendering. See the guide on for some background. You might also want to check out the before that. For advanced server rendering patterns,...
Welcome to the Advanced Server Rendering guide, where you will learn all about using React Query with streaming, Server Components and the Next.js app router. You might want to read the before this on...
