mirror of
https://github.com/hanzoai/next.js.git
synced 2026-09-24 17:00:51 +00:00
Andrew ClarkandGitHub
b301d3cfab
Flips the `experimental.prefetchInlining` default from `false` to `true`. This is the first step toward removing the flag entirely. Tests that explicitly set `prefetchInlining: true` have been cleaned up since they now match the default. Any CI failures from this PR will be addressed in follow-up PRs by temporarily opting out individual tests with `prefetchInlining: false` until they are migrated. <!-- NEXT_JS_LLM_PR -->
23 lines
770 B
JavaScript
23 lines
770 B
JavaScript
/**
|
|
* @type {import('next').NextConfig}
|
|
*/
|
|
const nextConfig = {
|
|
experimental: {
|
|
// The client segment cache currently only writes segment data during
|
|
// prefetches, not during navigations. The staleTimes feature is an
|
|
// exception: it preserves route cache entries for reuse across
|
|
// navigations. We rely on this to reproduce the bug — without it,
|
|
// dynamic route cache entries expire immediately, so the second lookup
|
|
// would always miss regardless of whether the key is correct.
|
|
//
|
|
// Once the client cache writes segment data during navigations more
|
|
// broadly, this test could be rewritten without this config.
|
|
prefetchInlining: false,
|
|
staleTimes: {
|
|
dynamic: 180,
|
|
},
|
|
},
|
|
}
|
|
|
|
module.exports = nextConfig
|