[Snyk] Upgrade org.webjars.npm:react-dom from 16.10.2 to 19.2.8

[mhill-os]

Snyk has created this PR to upgrade org.webjars.npm:react-dom from 16.10.2 to 19.2.8.

ℹ️ 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 21 versions ahead of your current version.

• The recommended version was released 21 days ago.

Breaking Change Risk

Notice: This assessment is enhanced by AI.

---

Important

• Warning: This PR contains a major version upgrade, and may be a breaking change.
• Check the changes in this PR to ensure they won't cause issues with your project.
• This PR was automatically created by Snyk using the credentials of a real user.

---

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:

• 🧐 View latest project report
• 📜 Customise PR templates
• 🛠 Adjust upgrade PR settings
• 🔕 Ignore this dependency or unsubscribe from future upgrade PRs

[mhill-os]

This is a major version upgrade from React 16 to 19, which includes multiple significant and breaking changes. A direct upgrade requires substantial code refactoring and thorough testing.

Key Breaking Changes:

• React 18: New Root API (Mandatory Change): The ReactDOM.render API, used in React 16, is deprecated in React 18 and fully removed in React 19. You must migrate to the new ReactDOM.createRoot API. This is the most critical change and is required to use the concurrent features introduced in React 18.

• React 19: Removal of Deprecated APIs:

  • ReactDOM.render and ReactDOM.unmountComponentAtNode are removed.
  • Legacy string refs are removed and must be replaced with createRef or callback refs.
  • React.FC and propTypes are also among the removed legacy APIs.

• React 17: Event Delegation Changes: React 17 changed how it attaches event handlers to the DOM. Instead of attaching to the document, events are attached to the root DOM container where your app is rendered. This can break integrations with non-React code that relies on document-level event listeners (e.g., for modals or analytics).

• React 18: Automatic Batching: State updates are now automatically batched together to reduce re-renders, even inside Promises, setTimeout, and native event handlers. This can change application behavior if your code previously relied on synchronous re-renders between state updates.

Recommendation:
This upgrade cannot be done automatically and poses a high risk of breaking the application. It is essential to perform a staged migration.

1. First, upgrade to react@18.3.0, which adds warnings for APIs that are removed in v19.
2. Address the mandatory migration from ReactDOM.render to ReactDOM.createRoot.
3. Refactor code to remove dependencies on legacy APIs like string refs and propTypes.
4. Thoroughly test the application, paying close attention to event handling and asynchronous state updates.

Notice 🤖: This content was augmented using artificial intelligence. AI-generated content may contain errors and should be reviewed for accuracy before use.

[mhill-os]

✅ Snyk checks have passed. No issues have been found so far.

Status	Scan Engine	Critical	High	Medium	Low	Total (0)
✅	Open Source Security	0	0	0	0	0 issues
✅	Licenses	0	0	0	0	0 issues

💻 Catch issues earlier using the plugins for VS Code, JetBrains IDEs, Visual Studio, and Eclipse.