SvelteKit defaults to rendering routes with SSR. Because of this, you need to disable the query on the server. Otherwise, your query will continue executing on the server asynchronously, even after the HTML has been sent to the client.
The recommended way to achieve this is to use the browser module from SvelteKit in your QueryClient object. This will not disable queryClient.prefetchQuery(), which is used in one of the solutions below.
src/routes/+layout.svelte
Svelte Query supports two ways of prefetching data on the server and passing that to the client with SvelteKit.
If you wish to view the ideal SSR setup, please have a look at the SSR example.
Together with SvelteKit's load, you can pass the data loaded server-side into createQuery's' initialData option:
src/routes/+page.ts
src/routes/+page.svelte
Pros:
Cons:
Svelte Query supports prefetching queries on the server. Using this setup below, you can fetch data and pass it into QueryClientProvider before it is sent to the user's browser. Therefore, this data is already available in the cache, and no initial fetch occurs client-side.
src/routes/+layout.ts
src/routes/+layout.svelte
src/routes/+page.ts
src/routes/+page.svelte
Pros:
Cons:
“This course is the best way to learn how to use React Query in real-world applications.”—Tanner LinsleyCheck it out