virtual-list icon indicating copy to clipboard operation
virtual-list copied to clipboard
verified publisher icon react-component

chore(deps-dev): bump react and react-dom

Open dependabot[bot] opened this issue 5 months ago • 2 comments

Bumps react and react-dom. These dependencies needed to be updated together. Updates react from 16.14.0 to 19.1.1

Release notes

Sourced from react's releases.

19.1.1 (July 28, 2025)

React

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

... (truncated)

Changelog

Sourced from react's changelog.

19.1.1 (July 28, 2025)

React

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 Compiler 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

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

... (truncated)

Commits
Maintainer changes

This version was pushed to npm by react-bot, a new releaser for react since your current version.


Updates react-dom from 16.14.0 to 19.1.1

Release notes

Sourced from react-dom's releases.

19.1.1 (July 28, 2025)

React

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

... (truncated)

Changelog

Sourced from react-dom's changelog.

19.1.1 (July 28, 2025)

React

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 Compiler 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

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

... (truncated)

Commits
Maintainer changes

This version was pushed to npm by react-bot, a new releaser for react-dom since your current version.


You can trigger a rebase of this PR 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)

Note Automatic rebases have been disabled on this pull request as it has been open for over 30 days.

dependabot[bot] avatar Jul 29 '25 02:07 dependabot[bot]

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

Name Status Preview Comments Updated (UTC)
virtual-list ❌ Failed (Inspect) Jul 29, 2025 2:30am

vercel[bot] avatar Jul 29 '25 02:07 vercel[bot]

[!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.

🪧 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.
    • Explain this complex logic.
    • 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 explain this code block.
    • @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 explain its main purpose.
    • @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.

Support

Need help? Join our Discord community for assistance with any issues or questions.

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 sequence diagram to generate a sequence diagram of the changes in this PR.
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @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.

coderabbitai[bot] avatar Jul 29 '25 02:07 coderabbitai[bot]