docs: add experimental staleTimes resource #64040
Merged
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
This stack of pull requests is managed by Graphite. Learn more about stacking. |
ztanner
requested review from
jh3y and
delbaoliveira
and removed request for
a team
ztanner
force-pushed
the
04-03-docs_fix_prefetching_information
branch
from
33c906c
to
616d5cc
Compare
ztanner
force-pushed
the
04-03-docs_add_experimental_staleTimes_resource
branch
2 times, most recently
from
1fae083
to
8e756d6
Compare
ijjk
approved these changes
Apr 3, 2024
ztanner
force-pushed
the
04-03-docs_fix_prefetching_information
branch
from
616d5cc
to
25e397b
Compare
ztanner
force-pushed
the
04-03-docs_add_experimental_staleTimes_resource
branch
from
8e756d6
to
bb487ac
Compare
Base automatically changed from
04-03-docs_fix_prefetching_information
to
canary
April 4, 2024 14:57
ztanner
force-pushed
the
04-03-docs_add_experimental_staleTimes_resource
branch
from
bb487ac
to
4aa72fa
Compare
epiloguess
pushed a commit
to epiloguess/next.js
that referenced
this pull request
Apr 5, 2024
This documents the behavior introduced in vercel#62856 to allow globally overriding the router cache invalidation period. `static` and `dynamic` in this case refer to variable levels of "liveness" and are unrelated to whether the segment itself is opting into static or dynamic rendering. In other words, the current `dynamic` default of 30s suggests that we consider the 30s delta to feel dynamic while still providing some caching for performance reasons. Others might prefer a value of 0s here, hence the configuration. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # --> Closes NEXT-2995
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
This documents the behavior introduced in #62856 to allow globally overriding the router cache invalidation period.
staticanddynamicin this case refer to variable levels of "liveness" and are unrelated to whether the segment itself is opting into static or dynamic rendering. In other words, the currentdynamicdefault of 30s suggests that we consider the 30s delta to feel dynamic while still providing some caching for performance reasons. Others might prefer a value of 0s here, hence the configuration.Closes NEXT-2995