Bump react and @types/react

[dependabot]

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

Release notes

Sourced from react's releases.

19.1.0 (March 28, 2025)

Owner Stack

An Owner Stack is a string representing the components that are directly responsible for rendering a particular component. You can log Owner Stacks when debugging or use Owner Stacks to enhance error overlays or other development tools. Owner Stacks are only available in development builds. Component Stacks in production are unchanged.

• An Owner Stack is a development-only stack trace that helps identify which components are responsible for rendering a particular component. An Owner Stack is distinct from a Component Stacks, which shows the hierarchy of components leading to an error.
• The captureOwnerStack API is only available in development mode and returns a Owner Stack, if available. The API can be used to enhance error overlays or log component relationships when debugging. #29923, #32353, #30306, #32538, #32529, #32538

React

• Enhanced support for Suspense boundaries to be used anywhere, including the client, server, and during hydration. #32069, #32163, #32224, #32252
• Reduced unnecessary client rendering through improved hydration scheduling #31751
• Increased priority of client rendered Suspense boundaries #31776
• Fixed frozen fallback states by rendering unfinished Suspense boundaries on the client. #31620
• Reduced garbage collection pressure by improving Suspense boundary retries. #31667
• Fixed erroneous “Waiting for Paint” log when the passive effect phase was not delayed #31526
• Fixed a regression causing key warnings for flattened positional children in development mode. #32117
• Updated useId to use valid CSS selectors, changing format from :r123: to «r123». #32001
• Added a dev-only warning for null/undefined created in useEffect, useInsertionEffect, and useLayoutEffect. #32355
• Fixed a bug where dev-only methods were exported in production builds. React.act is no longer available in production builds. #32200
• Improved consistency across prod and dev to improve compatibility with Google Closure Complier and bindings #31808
• Improve passive effect scheduling for consistent task yielding. #31785
• Fixed asserts in React Native when passChildrenWhenCloningPersistedNodes is enabled for OffscreenComponent rendering. #32528
• Fixed component name resolution for Portal #32640
• Added support for beforetoggle and toggle events on the dialog element. #32479 #32479

React DOM

• Fixed double warning when the href attribute is an empty string #31783
• Fixed an edge case where getHoistableRoot() didn’t work properly when the container was a Document #32321
• Removed support for using HTML comments (e.g. <!-- -->) as a DOM container. #32250
• Added support for <script> and \<template> tags to be nested within <select> tags. #31837
• Fixed responsive images to be preloaded as HTML instead of headers #32445

use-sync-external-store

• Added exports field to package.json for use-sync-external-store to support various entrypoints. #25231

React Server Components

• Added unstable_prerender, a new experimental API for prerendering React Server Components on the server #31724
• Fixed an issue where streams would hang when receiving new chunks after a global error #31840, #31851
• Fixed an issue where pending chunks were counted twice. #31833
• Added support for streaming in edge environments #31852
• Added support for sending custom error names from a server so that they are available in the client for console replaying. #32116
• Updated the server component wire format to remove IDs for hints and console.log because they have no return value #31671
• Exposed registerServerReference in client builds to handle server references in different environments. #32534
• Added react-server-dom-parcel package which integrates Server Components with the Parcel bundler #31725, #32132, #31799, #32294, #31741

19.0.0 (December 5, 2024)

Below is a list of all new features, APIs, deprecations, and breaking changes. Read React 19 release post and React 19 upgrade guide for more information.

Note: To help make the upgrade to React 19 easier, we’ve published a react@18.3 release that is identical to 18.2 but adds warnings for deprecated APIs and other changes that are needed for React 19. We recommend upgrading to React 18.3.1 first to help identify any issues before upgrading to React 19.

... (truncated)

Changelog

Sourced from react's changelog.

19.1.0 (March 28, 2025)

Owner Stack

An Owner Stack is a string representing the components that are directly responsible for rendering a particular component. You can log Owner Stacks when debugging or use Owner Stacks to enhance error overlays or other development tools. Owner Stacks are only available in development builds. Component Stacks in production are unchanged.

• An Owner Stack is a development-only stack trace that helps identify which components are responsible for rendering a particular component. An Owner Stack is distinct from a Component Stacks, which shows the hierarchy of components leading to an error.
• The captureOwnerStack API is only available in development mode and returns a Owner Stack, if available. The API can be used to enhance error overlays or log component relationships when debugging. #29923, #32353, #30306, #32538, #32529, #32538

React

• Enhanced support for Suspense boundaries to be used anywhere, including the client, server, and during hydration. #32069, #32163, #32224, #32252
• Reduced unnecessary client rendering through improved hydration scheduling #31751
• Increased priority of client rendered Suspense boundaries #31776
• Fixed frozen fallback states by rendering unfinished Suspense boundaries on the client. #31620
• Reduced garbage collection pressure by improving Suspense boundary retries. #31667
• Fixed erroneous “Waiting for Paint” log when the passive effect phase was not delayed #31526
• Fixed a regression causing key warnings for flattened positional children in development mode. #32117
• Updated useId to use valid CSS selectors, changing format from :r123: to «r123». #32001
• Added a dev-only warning for null/undefined created in useEffect, useInsertionEffect, and useLayoutEffect. #32355
• Fixed a bug where dev-only methods were exported in production builds. React.act is no longer available in production builds. #32200
• Improved consistency across prod and dev to improve compatibility with Google Closure Complier and bindings #31808
• Improve passive effect scheduling for consistent task yielding. #31785
• Fixed asserts in React Native when passChildrenWhenCloningPersistedNodes is enabled for OffscreenComponent rendering. #32528
• Fixed component name resolution for Portal #32640
• Added support for beforetoggle and toggle events on the dialog element. #32479 #32479

React DOM

• Fixed double warning when the href attribute is an empty string #31783
• Fixed an edge case where getHoistableRoot() didn’t work properly when the container was a Document #32321
• Removed support for using HTML comments (e.g. <!-- -->) as a DOM container. #32250
• Added support for <script> and \<template> tags to be nested within <select> tags. #31837
• Fixed responsive images to be preloaded as HTML instead of headers #32445

use-sync-external-store

• Added exports field to package.json for use-sync-external-store to support various entrypoints. #25231

React Server Components

• Added unstable_prerender, a new experimental API for prerendering React Server Components on the server #31724
• Fixed an issue where streams would hang when receiving new chunks after a global error #31840, #31851
• Fixed an issue where pending chunks were counted twice. #31833
• Added support for streaming in edge environments #31852
• Added support for sending custom error names from a server so that they are available in the client for console replaying. #32116
• Updated the server component wire format to remove IDs for hints and console.log because they have no return value #31671
• Exposed registerServerReference in client builds to handle server references in different environments. #32534
• Added react-server-dom-parcel package which integrates Server Components with the Parcel bundler #31725, #32132, #31799, #32294, #31741

19.0.0 (December 5, 2024)

Below is a list of all new features, APIs, deprecations, and breaking changes. Read React 19 release post and React 19 upgrade guide for more information.

... (truncated)

Commits

• 4a9df08 Stop creating Owner Stacks if many have been created recently (#32529)
• b630219 [refactor] move isValidElementType to react-is (#32518)
• 1a19170 [refactor] Add element type for Activity (#32499)
• 6aa8254 Add ref to Fragment (#32465)
• e0fe347 [flags] remove enableOwnerStacks (#32426)
• 70f1d76 [flow] Eliminate usage of global React types in ReactNativeTypes.js (#32330)
• 0d9834c build: add support to the rollup build for building typescript packages (#32393)
• a53da6a Add useSwipeTransition Hook Behind Experimental Flag (#32373)
• 32b0cad Enable owner stacks in Canary builds (#32053)
• ed8b68d Stop exporting dev-only methods in OSS production builds (#32200)
• Additional commits viewable in compare view

Updates @types/react from 18.3.18 to 19.0.12

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)

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Comments	Updated (UTC)
code-graph	❌ Failed (Inspect)			Apr 2, 2025 2:53am

[coderabbitai]

Important

Review skipped

Bot user detected.

To trigger a single review, invoke the @coderabbitai review command.

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>, please review it.
  • Generate unit testing code for this file.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai generate unit testing code for this file.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @coderabbitai read src/utils.ts and generate unit testing code.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  • @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai generate docstrings to generate docstrings for this PR.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai plan to trigger planning for file edits and PR creation.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.

[qodo-merge-pro]

CI Feedback 🧐

(Feedback updated until commit 9b6f7d1)

A test triggered by this PR failed. Here is an AI-generated analysis of the failure:

Action: build

Failed stage: Install dependencies [❌]

Failure summary: The action failed due to a dependency conflict during the npm ci command. Specifically: There's a version mismatch between React type definitions: - The project is using @types/react@19.0.12 - But @types/react-dom@18.3.5 requires @types/react@^18.0.0 as a peer dependency This creates an incompatible dependency tree because version 19 of @types/react doesn't satisfy the version 18 requirement from @types/react-dom. The error suggests fixing the upstream dependency conflict or using flags like --force or --legacy-peer-deps to bypass the issue.

Relevant error logs: 1: ##[group]Operating System 2: Ubuntu ... 151: with: 152: path: .next/cache 153: 154: key: Linux-nextjs-d7a1cce3bf4bf6d52e4c2a5b1c472397b7b3997e63d742f437ccf674e24fe06a-62b6284cb864ddee82b5c61687cdb20f4dd79be400b493c2b4cdc57d857ff8aa 155: restore-keys: Linux-nextjs-d7a1cce3bf4bf6d52e4c2a5b1c472397b7b3997e63d742f437ccf674e24fe06a- 156: 157: enableCrossOsArchive: false 158: fail-on-cache-miss: false 159: lookup-only: false 160: ##[endgroup] 161: Cache not found for input keys: Linux-nextjs-d7a1cce3bf4bf6d52e4c2a5b1c472397b7b3997e63d742f437ccf674e24fe06a-62b6284cb864ddee82b5c61687cdb20f4dd79be400b493c2b4cdc57d857ff8aa, Linux-nextjs-d7a1cce3bf4bf6d52e4c2a5b1c472397b7b3997e63d742f437ccf674e24fe06a- 162: ##[group]Run npm ci 163: �[36;1mnpm ci�[0m 164: shell: /usr/bin/bash -e {0} 165: ##[endgroup] 166: npm error code ERESOLVE 167: npm error ERESOLVE could not resolve 168: npm error 169: npm error While resolving: @types/react-dom@18.3.5 170: npm error Found: @types/react@19.0.12 171: npm error node_modules/@types/react 172: npm error dev @types/react@"^19.0.12" from the root project 173: npm error peerOptional @types/react@"*" from @radix-ui/react-arrow@1.1.2 174: npm error node_modules/@radix-ui/react-arrow 175: npm error @radix-ui/react-arrow@"1.1.2" from @radix-ui/react-popper@1.2.2 176: npm error node_modules/@radix-ui/react-popper 177: npm error @radix-ui/react-popper@"1.2.2" from @radix-ui/react-hover-card@1.1.6 178: npm error node_modules/@radix-ui/react-hover-card 179: npm error @radix-ui/react-hover-card@"^1.1.6" from the root project 180: npm error 3 more (@radix-ui/react-menu, @radix-ui/react-select, @radix-ui/react-tooltip) 181: npm error 37 more (@radix-ui/react-checkbox, ...) 182: npm error 183: npm error Could not resolve dependency: 184: npm error peer @types/react@"^18.0.0" from @types/react-dom@18.3.5 185: npm error node_modules/@types/react-dom 186: npm error dev @types/react-dom@"^18.3.5" from the root project 187: npm error peerOptional @types/react-dom@"*" from @radix-ui/react-arrow@1.1.2 188: npm error node_modules/@radix-ui/react-arrow 189: npm error @radix-ui/react-arrow@"1.1.2" from @radix-ui/react-popper@1.2.2 190: npm error node_modules/@radix-ui/react-popper 191: npm error @radix-ui/react-popper@"1.2.2" from @radix-ui/react-hover-card@1.1.6 192: npm error node_modules/@radix-ui/react-hover-card 193: npm error 3 more (@radix-ui/react-menu, @radix-ui/react-select, @radix-ui/react-tooltip) 194: npm error 18 more (@radix-ui/react-checkbox, ...) 195: npm error 196: npm error Conflicting peer dependency: @types/react@18.3.20 197: npm error node_modules/@types/react 198: npm error peer @types/react@"^18.0.0" from @types/react-dom@18.3.5 199: npm error node_modules/@types/react-dom 200: npm error dev @types/react-dom@"^18.3.5" from the root project 201: npm error peerOptional @types/react-dom@"*" from @radix-ui/react-arrow@1.1.2 202: npm error node_modules/@radix-ui/react-arrow 203: npm error @radix-ui/react-arrow@"1.1.2" from @radix-ui/react-popper@1.2.2 204: npm error node_modules/@radix-ui/react-popper 205: npm error @radix-ui/react-popper@"1.2.2" from @radix-ui/react-hover-card@1.1.6 206: npm error node_modules/@radix-ui/react-hover-card 207: npm error 3 more (@radix-ui/react-menu, @radix-ui/react-select, @radix-ui/react-tooltip) 208: npm error 18 more (@radix-ui/react-checkbox, ...) 209: npm error 210: npm error Fix the upstream dependency conflict, or retry 211: npm error this command with --force or --legacy-peer-deps 212: npm error to accept an incorrect (and potentially broken) dependency resolution. 213: npm error 214: npm error 215: npm error For a full report see: 216: npm error /home/runner/.npm/_logs/2025-04-02T02_51_10_196Z-eresolve-report.txt 217: npm error A complete log of this run can be found in: /home/runner/.npm/_logs/2025-04-02T02_51_10_196Z-debug-0.log 218: ##[error]Process completed with exit code 1. 219: Post job cleanup.