Am I understanding the caching docs correctly?
Unanswered
Pink-footed Shearwater posted this in #help-forum
Pink-footed ShearwaterOP
So I am researching the Next 15 caching updates, and to my understanding when you don't opt into Data Cache you will automatically be opted out of Full Route Cache.
To give you an example I use the Apollo client, which in previous Next versions you had to opt out of Full Route Cache using something like
Now in Next 15, because you need to opt into Data Cache and Apollo doesn't seem to do that you don't get full route cache and your route is always dynamic. Is this assumption correct or am I missing something here?
To give you an example I use the Apollo client, which in previous Next versions you had to opt out of Full Route Cache using something like
export const revalidate = 0 Now in Next 15, because you need to opt into Data Cache and Apollo doesn't seem to do that you don't get full route cache and your route is always dynamic. Is this assumption correct or am I missing something here?
5 Replies
American black bear
Caching is now opt in. So nothing is cached until you specify so. Your routes and fetches are always dynamic until you add "use cache" to them.
Pink-footed ShearwaterOP
Ahh I didn't know about the "use cache" directive yet.
I see it is still experimental. I did read about the opt in cache function in the fetch API, but that is not something I can use when fetching through the Apollo client.
American black bear
Actually it's my bad here. I just always used canary "use cache" with next.js 15 and thought it was the default now, but caching should still be opt-in for native fetch function.
I think apollo client caches the data by default using in memory cache. https://www.apollographql.com/docs/react/caching/overview