[Snyk] Upgrade react-dom from 19.2.0 to 19.2.1 #115
Conversation
Snyk has created this PR to upgrade react-dom from 19.2.0 to 19.2.1. See this package in npm: react-dom See this project in Snyk: https://app.snyk.io/org/bansikah22/project/0e6d3813-77e4-4c96-8b83-9bfcfc81bf97?utm_source=github&utm_medium=referral&page=upgrade-pr
|
Important Review skippedIgnore keyword(s) in the title. Please check the settings in the CodeRabbit UI or the You can disable this status message by setting the ✨ Finishing touches🧪 Generate unit tests (beta)
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. Comment |
![amazon-q-developer[bot]](https://avatars.githubusercontent.com/in/1220912?s=60&v=4){kind=small}
There was a problem hiding this comment.
Review Summary
This PR upgrades react-dom from 19.2.0 to 19.2.1, which is a good security practice to keep dependencies up-to-date. However, there's a critical version compatibility issue that must be resolved before merging.
Critical Issue Found:
- Version Mismatch: React (^19.1.0) and react-dom (^19.2.1) versions are incompatible, which could cause runtime errors
Recommendation:
Upgrade both React and react-dom to the same version (^19.2.1) to ensure compatibility. The suggested fix will align both packages to the same version range.
Once the version mismatch is resolved, this upgrade should be safe to merge as it includes important bug fixes and improvements from the React team.
You can now have the agent implement changes and create commits directly on your pull request's source branch. Simply comment with /q followed by your request in natural language to ask the agent to make changes.
| "react": "^19.1.0", | ||
| "react-dom": "^19.2.0", | ||
| "react-dom": "^19.2.1", |
There was a problem hiding this comment.
🛑 Version Mismatch: React and react-dom versions are incompatible. React is at ^19.1.0 while react-dom is being upgraded to ^19.2.1, creating a version mismatch that could cause runtime errors or unexpected behavior.
| "react": "^19.1.0", | |
| "react-dom": "^19.2.0", | |
| "react-dom": "^19.2.1", | |
| "react": "^19.2.1", | |
| "react-dom": "^19.2.1", |
Snyk has created this PR to upgrade react-dom from 19.2.0 to 19.2.1.
ℹ️ Keep your dependencies up-to-date. This makes it easier to fix existing vulnerabilities and to more quickly identify and fix newly disclosed vulnerabilities when they affect your project.
The recommended version is 1 version ahead of your current version.
The recommended version was released 24 days ago.
Release notes
Package name: react-dom
-
19.2.1 - 2025-12-03
-
19.2.0 - 2025-10-01
- React Performance tracks appear on the Performance panel’s timeline in your browser developer tools
- Added resume APIs for partial pre-rendering with Web Streams:
- Added resume APIs for partial pre-rendering with Node Streams:
- Updated
- 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
- Add Node Web Streams (
- Use underscore instead of
- Stringify context as "SomeContext" instead of "SomeContext.Provider" (@ kassens #33507)
- Include stack of cause of React instrumentation errors with
- Fix infinite
- Fix a bug when an initial value was passed to
- 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
- Block on Suspensey Fonts during reveal of server-side-rendered content (@ sebmarkbage #33342)
- Use underscore instead of
- Stop warning when ARIA 1.3 attributes are used (@ Abdul-Omira #34264)
- Allow
- Warn for using a React owned node as a Container if it also has text content (@ sebmarkbage #32774)
- s/HTML/text for for error messages if text hydration mismatches (@ rickhanlonii #32763)
- Fix a bug with
- Enable the
- Fix a bug with deeply nested Suspense inside Suspense fallback when server-side-rendering (@ gnoff #33467)
- Avoid hanging when suspending after aborting while rendering (@ gnoff #34192)
- Add Node Web Streams to server-side-rendering APIs for Node.js (@ sebmarkbage #33475)
- Preload
- Log error if production elements are rendered during development (@ eps1lon #34189)
- Fix a bug when returning a Temporary reference (e.g. a Client Reference) from Server Functions (@ sebmarkbage #34084, @ denk0403 #33761)
- Pass line/column to
- Support Async Modules in Turbopack Server References (@ lubieowoce #34531)
- Add support for .mjs file extension in Webpack (@ jennyscript #33028)
- Fix a wrong missing key warning (@ unstubbable #34350)
- Make console log resolve in predictable order (@ sebmarkbage #33665)
- createContainer and createHydrationContainer had their parameter order adjusted after
- Breaking: Require Node.js 18 or newer. (@ michaelfaith in #32458)
- Breaking: Flat config is now the default
- New Violations: Disallow calling
- New Violations: Disallow calling
- Handle
- Added
from react-dom GitHub release notesBelow 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.useEffectEventis a React Hook that lets you extract non-reactive logic into an Effect Event.cacheSignal(for RSCs) lets your know when thecache()lifetime is over.New React DOM Features
resume: to resume a prerender to a stream.resumeAndPrerender: to resume a prerender to HTML.resumeToPipeableStream: to resume a prerender to a stream.resumeAndPrerenderToNodeStream: to resume a prerender to HTML.prerenderAPIs to return apostponedstate that can be passed to theresumeAPIs.Notable changes
<ViewTransition>Component. React will batch as much reveals as possible before the first paint while trying to hit popular first-contentful paint metrics.prerender,renderToReadableStream) to server-side-rendering APIs for Node.js:IDs generated by useIdAll Changes
React
<Activity />was developed over many years, starting beforeClassComponent.setState(@ acdlite @ sebmarkbage and many others)%oplaceholder (@ eps1lon #34198)useDeferredValueloop in popstate event (@ acdlite #32821)useDeferredValue(@ acdlite #34376)cacheSignal(@ sebmarkbage #33557)React DOM
:for IDs generated byuseId(@ sebmarkbage, @ eps1lon: #32001, #33342#33099, #33422)nonceto be used on hoistable styles (@ Andarist #32461)React.useinsideReact.lazy-ed Component (@ hi-ogawa #33941)progressiveChunkSizeoption for server-side-rendering APIs (@ sebmarkbage #33027)React Server Components
<img>and<link>using hints before they're rendered (@ sebmarkbage #34604)filterStackFrame(@ eps1lon #33707)React Reconciler
on*handlers to account for upcoming experimental APIseslint-plugin-react-hooks@6.1.0
Note: Version 6.0.0 was mistakenly released and immediately deprecated and untagged on npm. This is the first official 6.x major release and includes breaking changes.
recommendedpreset. Legacy config moved torecommended-legacy. (@ michaelfaith in #32457)usewithin try/catch blocks. (@ poteto in #34040)useEffectEventfunctions in arbitrary closures. (@ jbrown215 in #33544)React.useEffectin addition touseEffectin rules-of-hooks. (@ Ayc0 in #34076)react-hookssettings config option that to acceptadditionalEffectHooksthat are used across exhaustive-deps and rules-of-hooks rules. (@ jbrown215) in #34497Important
Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open upgrade PRs.
For more information: