next.js
19f93c89 - fetch cache: revalidate should take precedence over force-dynamic (#72357)

Commit
1 year ago
fetch cache: revalidate should take precedence over force-dynamic (#72357) `force-dynamic` will automatically disable caching on a fetch. If `force-dynamic` is set, and there's a `revalidate` value on the fetch, the revalidate value will be a no-op unless you explicitly opt into caching via `cache: 'force-cache'`. This changes the behavior to favor a positive revalidate value over `force-dynamic` when deciding to cache the fetch.
Author
Parents
Loading