chore(deps): bump react-dom and @types/react-dom

[dependabot]

Bumps react-dom and @types/react-dom. These dependencies needed to be updated together.
Updates react-dom from 18.3.1 to 19.2.0

Release notes

Sourced from react-dom's releases.

19.2.0 (Oct 1, 2025)

Below is a list of all new features, APIs, and bug fixes.

Read the React 19.2 release post for more information.

New React Features

• <Activity>: A new API to hide and restore the UI and internal state of its children.
• useEffectEvent is a React Hook that lets you extract non-reactive logic into an Effect Event.
• cacheSignal (for RSCs) lets your know when the cache() lifetime is over.
• React Performance tracks appear on the Performance panel’s timeline in your browser developer tools

New React DOM Features

• Added resume APIs for partial pre-rendering with Web Streams:
  • resume: to resume a prerender to a stream.
  • resumeAndPrerender: to resume a prerender to HTML.
• Added resume APIs for partial pre-rendering with Node Streams:
  • resumeToPipeableStream: to resume a prerender to a stream.
  • resumeAndPrerenderToNodeStream: to resume a prerender to HTML.
• Updated prerender APIs to return a postponed state that can be passed to the resume APIs.

Notable changes

• React DOM now batches suspense boundary reveals, matching the behavior of client side rendering. This change is especially noticeable when animating the reveal of Suspense boundaries e.g. with the upcoming <ViewTransition> Component. React will batch as much reveals as possible before the first paint while trying to hit popular first-contentful paint metrics.
• Add Node Web Streams (prerender, renderToReadableStream) to server-side-rendering APIs for Node.js
• Use underscore instead of : IDs generated by useId

All Changes

React

• <Activity /> was developed over many years, starting before ClassComponent.setState (@​acdlite @​sebmarkbage and many others)
• Stringify context as "SomeContext" instead of "SomeContext.Provider" (@​kassens #33507)
• Include stack of cause of React instrumentation errors with %o placeholder (@​eps1lon #34198)
• Fix infinite useDeferredValue loop in popstate event (@​acdlite #32821)
• Fix a bug when an initial value was passed to useDeferredValue (@​acdlite #34376)
• Fix a crash when submitting forms with Client Actions (@​sebmarkbage #33055)
• Hide/unhide the content of dehydrated suspense boundaries if they resuspend (@​sebmarkbage #32900)
• Avoid stack overflow on wide trees during Hot Reload (@​sophiebits #34145)
• Improve Owner and Component stacks in various places (@​sebmarkbage, @​eps1lon: #33629, #33724, #32735, #33723)
• Add cacheSignal (@​sebmarkbage #33557)

React DOM

• Block on Suspensey Fonts during reveal of server-side-rendered content (@​sebmarkbage #33342)
• Use underscore instead of : for IDs generated by useId (@​sebmarkbage, @​eps1lon: #32001, facebook/react#33342#33099, #33422)
• Stop warning when ARIA 1.3 attributes are used (@​Abdul-Omira #34264)
• Allow nonce to be used on hoistable styles (@​Andarist #32461)
• Warn for using a React owned node as a Container if it also has text content (@​sebmarkbage #32774)

... (truncated)

Changelog

Sourced from react-dom's changelog.

19.2.0 (October 1st, 2025)

Below is a list of all new features, APIs, and bug fixes.

Read the React 19.2 release post for more information.

New React Features

• <Activity>: A new API to hide and restore the UI and internal state of its children.
• useEffectEvent is a React Hook that lets you extract non-reactive logic into an Effect Event.
• cacheSignal (for RSCs) lets your know when the cache() lifetime is over.
• React Performance tracks appear on the Performance panel’s timeline in your browser developer tools

New React DOM Features

• Added resume APIs for partial pre-rendering with Web Streams:
  • resume: to resume a prerender to a stream.
  • resumeAndPrerender: to resume a prerender to HTML.
• Added resume APIs for partial pre-rendering with Node Streams:
  • resumeToPipeableStream: to resume a prerender to a stream.
  • resumeAndPrerenderToNodeStream: to resume a prerender to HTML.
• Updated prerender APIs to return a postponed state that can be passed to the resume APIs.

Notable changes

• React DOM now batches suspense boundary reveals, matching the behavior of client side rendering. This change is especially noticeable when animating the reveal of Suspense boundaries e.g. with the upcoming <ViewTransition> Component. React will batch as much reveals as possible before the first paint while trying to hit popular first-contentful paint metrics.
• Add Node Web Streams (prerender, renderToReadableStream) to server-side-rendering APIs for Node.js
• Use underscore instead of : IDs generated by useId

All Changes

React

• <Activity /> was developed over many years, starting before ClassComponent.setState (@​acdlite @​sebmarkbage and many others)
• Stringify context as "SomeContext" instead of "SomeContext.Provider" (@​kassens #33507)
• Include stack of cause of React instrumentation errors with %o placeholder (@​eps1lon #34198)
• Fix infinite useDeferredValue loop in popstate event (@​acdlite #32821)
• Fix a bug when an initial value was passed to useDeferredValue (@​acdlite #34376)
• Fix a crash when submitting forms with Client Actions (@​sebmarkbage #33055)
• Hide/unhide the content of dehydrated suspense boundaries if they resuspend (@​sebmarkbage #32900)
• Avoid stack overflow on wide trees during Hot Reload (@​sophiebits #34145)
• Improve Owner and Component stacks in various places (@​sebmarkbage, @​eps1lon: #33629, #33724, #32735, #33723)
• Add cacheSignal (@​sebmarkbage #33557)

React DOM

• Block on Suspensey Fonts during reveal of server-side-rendered content (@​sebmarkbage #33342)
• Use underscore instead of : for IDs generated by useId (@​sebmarkbage, @​eps1lon: #32001, facebook/react#33342#33099, #33422)
• Stop warning when ARIA 1.3 attributes are used (@​Abdul-Omira #34264)
• Allow nonce to be used on hoistable styles (@​Andarist #32461)

... (truncated)

Commits

• 8618113 Bump scheduler version (#34671)
• 1bd1f01 Ship partial-prerendering APIs to Canary (#34633)
• 2f0649a [Fizz] Remove nonce option from resume-and-prerender APIs (#34664)
• 5667a41 Bump next prerelease version numbers (#34639)
• e08f53b Match react-dom/static test entrypoints and published entrypoints (#34599)
• 8bb7241 Bump useEffectEvent to Canary (#34610)
• 83c88ad Handle fabric root level fragment with compareDocumentPosition (#34533)
• 68f00c9 Release Activity in Canary (#34374)
• 3168e08 [flags] enable opt-in for enableDefaultTransitionIndicator (#34373)
• 3434ff4 Add scrollIntoView to fragment instances (#32814)
• Additional commits viewable in compare view

Updates @types/react-dom from 18.3.7 to 19.2.3

Commits

• See full diff in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

[dependabot]

Labels

The following labels could not be found: dependencies, npm. Please create them before Dependabot can add them to a pull request.

Please fix the above issues or remove invalid values from dependabot.yml.

[mchestr]

@dependabot rebase

[dependabot]

Looks like this PR is already up-to-date with main! If you'd still like to recreate it from scratch, overwriting any edits, you can request @dependabot recreate.

[mchestr]

@dependabot recreate

[mchestr]

@dependabot rebase

[mchestr]

@dependabot rebase

[mchestr]

https://github.com/dependabot rebase

[mchestr]

@dependabot rebase

[claude]

PR Review: React 19.2.0 Upgrade

Summary

This PR upgrades React and React DOM from 18.3.x to 19.2.0, along with the corresponding TypeScript type definitions. This is a major version upgrade that introduces significant changes and new features.

---

✅ Positive Observations

1. Dependency Consistency: Both react and react-dom are upgraded together (to 19.2.0), and type definitions match (@types/react 19.2.7 and @types/react-dom 19.2.3).

2. Clean Dependency Tree: The upgrade removes @types/prop-types dependency and simplifies the dependency tree by removing loose-envify as a direct dependency (now only dev).

3. Package Lock Updated: The package-lock.json is properly updated with all transitive dependencies.

---

⚠️ Concerns & Recommendations

1. Next.js Compatibility (CRITICAL)

• Issue: Next.js 16.0.3 may not be fully compatible with React 19.2.0
• Current: next: ^16.0.3, which is likely a canary/beta version
• Recommendation: Verify Next.js 16 officially supports React 19. Check Next.js release notes and test thoroughly.
• Action Required: Run the full build and test suite to ensure compatibility

2. Breaking Changes in React 19

React 19 includes several breaking changes that may affect this codebase:

• useId format change: Now uses underscores (_) instead of colons (:). This could affect CSS selectors or test assertions that rely on ID format.
• New hooks: useEffectEvent is now available - consider if any effect-related code could benefit from refactoring.
• Suspense behavior changes: Boundary reveals are now batched differently, which may affect loading states.
• Server Components: Enhanced partial pre-rendering APIs - ensure server/client component boundaries are correct.

3. Test Coverage (CRITICAL)

• Missing: No evidence of test execution in this PR
• Required Actions:
  • Run unit tests: npm test
  • Run E2E tests: npm run test:e2e
  • Run build: npm run build
  • Check for TypeScript errors
  • Verify all client components still work correctly

4. Framer Motion Compatibility

• Current: framer-motion: ^12.23.24
• Concern: This version may have been designed for React 18. Check if Framer Motion 12.x supports React 19.
• Project Impact: The codebase heavily uses Framer Motion for animations (wrapped sections, transitions, etc.)
• Recommendation: Review Framer Motion's React 19 compatibility or test animations thoroughly.

5. Third-Party Library Compatibility

Libraries that may need verification:

• @tanstack/react-query (5.56.0): Verify React 19 support
• react-chartjs-2 (5.3.1): Check compatibility
• react-markdown (10.1.0): Verify rendering still works
• react-countup (6.5.3): Check for issues
• @testing-library/react (16.3.0): Should support React 19, but verify

6. Security & Performance

• Positive: No known security vulnerabilities introduced
• Performance: React 19 includes performance improvements, but batching changes may affect perceived performance
• Recommendation: Monitor performance metrics after deployment

---

🔧 Required Testing Checklist

Before merging, please verify:

• npm run build completes successfully
• npm test passes all unit tests
• npm run test:e2e passes all E2E tests
• No new TypeScript errors introduced
• Client components with hooks still work ('use client' components)
• Framer Motion animations render correctly
• TanStack Query data fetching works as expected
• NextAuth authentication flow works
• Server Actions continue to function
• Form submissions work correctly
• Charts render properly (react-chartjs-2)
• Wrapped generation and display works
• Admin dashboard functions correctly
• Onboarding flow completes successfully

---

📋 Migration Considerations

If you proceed with this upgrade, consider:

1. Code Review: Search for patterns that might be affected:

   • useId() usage - verify IDs are not used in CSS selectors
   • Custom hooks that could benefit from useEffectEvent
   • Suspense boundaries - test loading states

2. Documentation: Update any developer documentation mentioning React version requirements

3. Rollback Plan: Ensure you can quickly revert if issues are found in production

---

🎯 Verdict

HOLD - Do Not Merge Yet

While the dependency upgrade itself is clean, this is a major version change with significant implications:

1. Must verify Next.js 16.0.3 officially supports React 19
2. Must run full test suite and build before merging
3. Must test Framer Motion compatibility (heavily used in this project)
4. Should verify third-party library compatibility
5. Consider staging deployment first before production

Recommended Action: Run the test suite and build, verify no breaking changes, and test critical user flows manually before merging.

---

📚 Additional Resources

• React 19.2 Release Post
• React 19 Upgrade Guide
• Next.js React 19 Support

---

Review conducted following project CLAUDE.md guidelines. Focused on TypeScript strict mode, Next.js App Router patterns, and project architecture.