Searchparams not working when `cacheComponents` and `draftMode` are enabled
Open
@icyJoseph is already working on this.
Since Sep 16, 2026.
Draft Mode
- Dominant language
- JavaScript
- Stars
- 142k
- Forks
- 32.4k
- Avg merge
- 2d 14h
- Merged PRs (30d)
- 351
Description
Link to the code that reproduces this issue
https://github.com/joostmeijles/nextjs-await-searchparams-bug
To Reproduce
- Open https://nextjs-await-searchparams-bug.vercel.app/api/draft -> enables Draft Mode and redirects to
/. - Click
Overview - Click every category in the list, e.g. "A".
- Expected:
Category (via await searchParams): <selected category> - Actual: shows always the same category
- Expected:
- Hard-reload the URL: the correct content now renders.
Current vs. Expected behavior
Current: page always shows same content, selecting another page by using a search param does not work
Expected: page content changes when a different search param is selected
Provide environment information
Operating System:
Platform: win32
Arch: x64
Version: Windows 11 Pro
Available memory (MB): 64949
Available CPU cores: 16
Binaries:
Node: 24.21.0
npm: 11.19.0
Yarn: N/A
pnpm: 12.3.4
Relevant Packages:
next: 16.4.0-canary.33 // Latest available version is detected (16.4.0-canary.33).
eslint-config-next: N/A
react: 19.3.0
react-dom: 19.3.0
typescript: 5.9.3
Next.js Config:
output: N/A
Which area(s) are affected? (Select all that apply)
cacheComponents, Draft Mode
Which stage(s) are affected? (Select all that apply)
next start (local), Vercel (Deployed)
Additional context
No response
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Assessment
This issue has not been assessed yet.