Support `experimental.hydrationChangeEvent` React experimental channel opt-in
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 67/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Active
- Tech stack
- next.js, react, typescript
- Domain
- backend, build-system
Research direction
Start with the configuration handling for experimental.useExperimentalReact from related issue #2109 and the App Router coverage for React channel selection. Add recognition of experimental.hydrationChangeEvent and verify that true selects the experimental channel while false or absent preserves the current channel unless another opt-in applies. Done means App Router tests cover enabled and disabled configurations.
Written by the indexing model from the issue text.
Description
Next.js Change
What changed
Next.js added experimental.hydrationChangeEvent. When enabled for the App Router, it selects React's experimental release channel so React's internal enableHydrationChangeEvent flag is available. The option has no independent runtime behavior beyond selecting that React build.
Impact on vinext
vinext must recognize this Next.js experimental configuration option and ensure it selects the same React release channel as other experimental React opt-ins. Configs using the flag should not be rejected or silently run against the wrong React build.
Acceptance criteria
- Accept
experimental.hydrationChangeEventin vinext configuration. - When true for an App Router application, select React's experimental channel consistently with Next.js.
- When false or absent, preserve the current React channel unless another experimental React option requires it.
- Add App Router coverage for the enabled and disabled configurations.
Related
- #2109 - Support
experimental.useExperimentalReactto opt into React's experimental channel - vercel/next.js#99610 - upstream change
- Dominant language
- TypeScript
- Stars
- 9.3k
- Forks
- 461
- Avg merge
- 1d 46m
- Merged PRs (30d)
- 487
Getting set up
- No Dockerfile or Docker Compose file
- No pull request template
- Read the contributing 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.
More from cloudflare/vinext
-
The `next-js` export condition isn't set, so packages like next-sanity load their non-Next buildPossibly taken @james-elicx claimed this 4 days ago. Open
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
cloudflare/vinext#4302 · 1 comment ·
Maintainers usually reply within 1 day
-
[nextjs-tracker] Fix navigation from global-not-found to app routesPossibly taken @kanchingyg claimed this 5 days ago. Open
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
cloudflare/vinext#4233 ·
Maintainers usually reply within 1 day
-
nextjs-tracking
Difficulty 2/5 1-3 hours Newbie friendliness 69/100
cloudflare/vinext#3920 ·
Maintainers usually reply within 1 day
-
docs: document deployment with Cloudflare Workers Builds / Git integrationPossibly taken @reginaldalfret claimed this 22 days ago. Open
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
cloudflare/vinext#3738 ·
Maintainers usually reply within 1 day
-
Standalone server.js does not default NODE_ENV to productionPossibly taken @reginaldalfret claimed this 34 days ago. Open
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
cloudflare/vinext#3444 ·
Maintainers usually reply within 1 day
All issues in cloudflare/vinext
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day
-
area:web p3
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Lets-Parley/Parley#912 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
wealthfolio/wealthfolio#2376 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
be-BOP-io-SA/be-BOP#2817 ·
Maintainers usually reply within 5 days
-
documentation good first issue
Difficulty 1/5 1-3 hours Newbie friendliness 84/100
sno-ai/sno-station#149 · 1 comment ·
Maintainers usually reply within 1 day