-
Notifications
You must be signed in to change notification settings - Fork 29.9k
Open
Labels
Route GroupsRelated to Route Groups.Related to Route Groups.
Description
Link to the code that reproduces this issue
https://codesandbox.io/p/devbox/sharp-neumann-7ks2ds
To Reproduce
- Start the application in development
- Open devtools
- Open page /
- Click on page 0
- Navigate back to /
- Click on page 1
Page 0
Page 1
This only happens when using page groups
- app/
- (pages)/
- 0/
- page.tsx
- 1/
- page.tsxand dynamic staleTimes set to anything non-zero
const nextConfig = {
reactStrictMode: false,
experimental: {
staleTimes: {
dynamic: 60,
},
},
}Current vs. Expected behavior
Only one server component request is issued.
Provide environment information
Operating System:
Platform: linux
Arch: x64
Version: #1 SMP PREEMPT_DYNAMIC Sun Aug 6 20:05:33 UTC 2023
Available memory (MB): 4102
Available CPU cores: 2
Binaries:
Node: 20.12.0
npm: 10.5.0
Yarn: 1.22.19
pnpm: 8.15.6
Relevant Packages:
next: 16.0.3 // Latest available version is detected (16.0.3).
eslint-config-next: 15.2.0
react: 19.2.0
react-dom: 19.2.0
typescript: 5.8.3
Next.js Config:
output: N/AWhich area(s) are affected? (Select all that apply)
Route Groups
Which stage(s) are affected? (Select all that apply)
next dev (local), next start (local)
Additional context
This happens in dev and prod, with cacheComponents enabled and disabled, with and without a wrapping suspense boundary.
Setting a debugger on
| cacheNode.lazyData = lazyData = fetchServerResponse( |
resolvedRsc really is null for the second request, even though the first request returned just fine.Metadata
Metadata
Assignees
Labels
Route GroupsRelated to Route Groups.Related to Route Groups.