SSR using NextJS App Router with InitialData Does not Callback about query HOT 4 CLOSED

initialData is always taken into account when a new cache entry is created. If you change the key, you get a new cache entry. Thus, all your keys (["key", 1], ["key", 2]etc) will get"Hardcoded Initial Data" put into the cache. And then, you're saying that data in the cache is fresh forever (staleTime: Infinity), so there's no need to run the queryFn`.

from query.

@TkDodo What would be the suggested configuration to get initial data from SSR and then subsequent calls to update that data? I've read the documentation, it says that initialData can be used as long as it is passed along the React components, thus I though I could use it to fill the cache from the SSR.

For additional context, the real use case is a grid with filters. The filters change the cache key but on the initial load (server) there is some data for the grid.

from query.

it says that initialData can be used as long as it is passed along the React components

have you read the guide along with all the drawbacks of initialData?

• https://tanstack.com/query/v5/docs/framework/react/guides/ssr#get-started-fast-with-initialdata

you likely want hydration:

• https://tanstack.com/query/v5/docs/framework/react/guides/ssr#using-the-hydration-apis

from query.

@TkDodo I have read the documentation and people in my team as well.

We are not using V5 yet and we all understood that we could use initialData without adding the hydration API into our code base. If we must use hydration, we can but will need to plan additional time for the task. It's fine, if that is the direction but we were under the impression that we could make it work direclty with the initialData

from query.