You are currently viewing documentation for version 14 of Next.js.
StaleTimes (experimental)
Warning: The
staleTimes
configuration is an experimental feature. This configuration strategy will likely change in the future.
staleTimes
is an experimental feature that allows configuring the invalidation period of the client router cache.
This configuration option is available as of v14.2.0-canary.53.
You can enable this experimental feature & provide custom revalidation times by setting the experimental staleTimes
flag:
next.config.js
/** @type {import('next').NextConfig} */
const nextConfig = {
experimental: {
staleTimes: {
dynamic: 30,
static: 180,
},
},
}
module.exports = nextConfig
The static
and dynamic
properties correspond with the time period (in seconds) based on different types of link prefetching.
- The
dynamic
property is used when the page is neither statically generated nor fully prefetched (i.e., with prefetch=).- Default: 0 seconds (not cached)
- The
static
property is used for statically generated pages, or when theprefetch
prop onLink
is set totrue
, or when callingrouter.prefetch
.- Default: 5 minutes
Good to know:
- Loading boundaries are considered reusable for the
static
period defined in this configuration.- This doesn't affect partial rendering, meaning shared layouts won't automatically be refetched on every navigation, only the page segment that changes.
- This doesn't change back/forward caching behavior to prevent layout shift and to prevent losing the browser scroll position.
You can learn more about the Client Router Cache here.
Version History
Version | Changes |
---|---|
v14.2.0 | experimental staleTimes introduced |
Was this helpful?