Using force-cache prevents revalidation about next.js

[ShubhamOulkar]

Use only-cache:-

This option sets 'force-cache' if no option is provided on fetch() request.
Where as default-cache sets 'force-cache' if no option is provided on fetch() request but it consider as static even after dynamic functions.

Use following in next-canary only (this creates dynamic rendering with cached data)

export const fetchCache = "only-cache";

Don't need to use fetchCache option in Next 14 because fetch() cached by default, use of dynamic functions will render dynamically.

[willemmulder]

@ShubhamOulkar Thanks, but I'm not sure if I understand correctly. So what I want is that all requests (also those after dynamic functions) are always cached (unless they specifically opt out using no-store), but that the cache is invalidated every 5 minutes. How would I do that in Next 14?

Note that I do use cookies/sessions/auth, so the functions are always rendered dynamically, but I do want the requests to be cached for 5 minutes.

What do you mean with the "but it consider as static even after dynamic functions." part?