-
Notifications
You must be signed in to change notification settings - Fork 30.2k
Labels
Description
Link to the code that reproduces this issue
https://github.com/joostmeijles/nextjs-rsc-revalidate-issue
To Reproduce
- Go to https://nextjs-rsc-revalidate-issue.vercel.app/
- Click on the "Go to /example" link
- Observe that
example?_rsc=is being fetched - Go in a 2nd browser tab to https://nextjs-rsc-revalidate-issue.vercel.app/revalidate to trigger a cache revalidate and a ISR re-render of the /example page
- Go in a 3rd browser tab to https://nextjs-rsc-revalidate-issue.vercel.app/example and observe that the page is re-rendered with new content
- Navigate back from the /example page to /7. Wait for 5 minutes (the client-side cache duration specified by https://nextjs.org/docs/app/deep-dive/caching#duration-3)
- Navigate in the 1st browser tab to /example (by clicking the link)
- Observe that NO new fetch is done for
example?_rsc=
Current vs. Expected behavior
Current: example page is not refreshed after 5 minutes
Expected: example page is refreshed after 5 minutes
Provide environment information
Operating System:
Platform: win32
Arch: x64
Version: Windows 11 Enterprise
Available memory (MB): 32472
Available CPU cores: 16
Binaries:
Node: 22.13.1
npm: 10.9.2
Yarn: 1.22.19
pnpm: 9.15.5
Relevant Packages:
next: 15.4.0-canary.31 // Latest available version is detected (15.4.0-canary.31).
eslint-config-next: N/A
react: 19.1.0
react-dom: 19.1.0
typescript: 5.8.3
Next.js Config:
output: N/AWhich area(s) are affected? (Select all that apply)
SWC, Not sure
Which stage(s) are affected? (Select all that apply)
next start (local), Vercel (Deployed)
Additional context
No response