Fix: 'force-dynamic' does not opt out of the data cache #75370
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
https://nextjs.org/docs/app/building-your-application/caching#segment-config-options Setting fetchCache = 'default-no-store' opts out of the data cache. I tested and confirmed this behavior live on my web app. A page with dynamic = "force-dynamic" that uses unstable_cache will read the cached value (data cache) without calling the async fetcher function until the key has been invalidated (and purged). The only difference 'force-dynamic' caused on my page was disable the full route cache, forcing the page to re-check the data cache. With tag-based invalidation, only the invalidated tags in the data cache had their fetch functions called. i.e. 'force-dynamic' does not opt out of the data cache
|
Allow CI Workflow Run
Note: this should only be enabled once the PR is ready to go and can only be enabled by a maintainer |
1 similar comment
|
Allow CI Workflow Run
Note: this should only be enabled once the PR is ready to go and can only be enabled by a maintainer |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
https://nextjs.org/docs/app/building-your-application/caching#segment-config-options
Setting fetchCache = 'default-no-store' opts out of the data cache.
I tested and confirmed this behavior live on my web app.
A page with dynamic = "force-dynamic" that uses unstable_cache will read the cached value (data cache) without calling the async fetcher function until the key has been invalidated (and purged).
The only difference 'force-dynamic' caused on my page was disable the full route cache, forcing the page to re-check the data cache. With tag-based invalidation, only the invalidated tags in the data cache had their fetch functions called.
i.e. 'force-dynamic' does not opt out of the data cache