fix(deps): update react monorepo to v18 (major)

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
react (source)	^17.0.2 -> ^18.0.0
react-dom (source)	^17.0.2 -> ^18.0.0

---

Release Notes

facebook/react (react)

v18.3.1

Compare Source

v18.3.0

Compare Source

v18.2.0

Compare Source

React DOM

• Provide a component stack as a second argument to onRecoverableError. (@​gnoff in #​24591)
• Fix hydrating into document causing a blank page on mismatch. (@​gnoff in #​24523)
• Fix false positive hydration errors with Suspense. (@​gnoff in #​24480 and @​acdlite in #​24532)
• Fix ignored setState in Safari when adding an iframe. (@​gaearon in #​24459)

React DOM Server

• Pass information about server errors to the client. (@​salazarm and @​gnoff in #​24551 and #​24591)
• Allow to provide a reason when aborting the HTML stream. (@​gnoff in #​24680)
• Eliminate extraneous text separators in the HTML where possible. (@​gnoff in #​24630)
• Disallow complex children inside <title> elements to match the browser constraints. (@​gnoff in #​24679)
• Fix buffering in some worker environments by explicitly setting highWaterMark to 0. (@​jplhomer in #​24641)

Server Components (Experimental)

• Add support for useId() inside Server Components. (@​gnoff in #​24172)

v18.1.0

Compare Source

React DOM

• Fix the false positive warning about react-dom/client when using UMD bundle. (@​alireza-molaee in #​24274)
• Fix suppressHydrationWarning to work in production too. (@​gaearon in #​24271)
• Fix componentWillUnmount firing twice inside of Suspense. (@​acdlite in #​24308)
• Fix some transition updates being ignored. (@​acdlite in #​24353)
• Fix useDeferredValue causing an infinite loop when passed an unmemoized value. (@​acdlite in #​24247)
• Fix throttling of revealing Suspense fallbacks. (@​sunderls in #​24253)
• Fix an inconsistency in whether the props object is the same between renders. (@​Andarist and @​acdlite in #​24421)
• Fix a missing warning about a setState loop in useEffect. (@​gaearon in #​24298)
• Fix a spurious hydration error. (@​gnoff in #​24404)
• Warn when calling setState in useInsertionEffect. (@​gaearon in #​24295)
• Ensure the reason for hydration errors is always displayed. (@​gaearon in #​24276)

React DOM Server

• Fix escaping for the bootstrapScriptContent contents. (@​gnoff in #​24385)
• Significantly improve performance of renderToPipeableStream. (@​gnoff in #​24291)

ESLint Plugin: React Hooks

• Fix false positive errors with a large number of branches. (@​scyron6 in #​24287)
• Don't consider a known dependency stable when the variable is reassigned. (@​afzalsayed96 in #​24343)

Use Subscription

• Replace the implementation with the use-sync-external-store shim. (@​gaearon in #​24289)

v18.0.0

Compare Source

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

New Features

React

• useId is a new hook for generating unique IDs on both the client and server, while avoiding hydration mismatches. It is primarily useful for component libraries integrating with accessibility APIs that require unique IDs. This solves an issue that already exists in React 17 and below, but it’s even more important in React 18 because of how the new streaming server renderer delivers HTML out-of-order.
• startTransition and useTransition let you mark some state updates as not urgent. Other state updates are considered urgent by default. React will allow urgent state updates (for example, updating a text input) to interrupt non-urgent state updates (for example, rendering a list of search results).
• useDeferredValue lets you defer re-rendering a non-urgent part of the tree. It is similar to debouncing, but has a few advantages compared to it. There is no fixed time delay, so React will attempt the deferred render right after the first render is reflected on the screen. The deferred render is interruptible and doesn't block user input.
• useSyncExternalStore is a new hook that allows external stores to support concurrent reads by forcing updates to the store to be synchronous. It removes the need for useEffect when implementing subscriptions to external data sources, and is recommended for any library that integrates with state external to React.
• useInsertionEffect is a new hook that allows CSS-in-JS libraries to address performance issues of injecting styles in render. Unless you’ve already built a CSS-in-JS library we don’t expect you to ever use this. This hook will run after the DOM is mutated, but before layout effects read the new layout. This solves an issue that already exists in React 17 and below, but is even more important in React 18 because React yields to the browser during concurrent rendering, giving it a chance to recalculate layout.

React DOM Client

These new APIs are now exported from react-dom/client:

• createRoot: New method to create a root to render or unmount. Use it instead of ReactDOM.render. New features in React 18 don't work without it.
• hydrateRoot: New method to hydrate a server rendered application. Use it instead of ReactDOM.hydrate in conjunction with the new React DOM Server APIs. New features in React 18 don't work without it.

Both createRoot and hydrateRoot accept a new option called onRecoverableError in case you want to be notified when React recovers from errors during rendering or hydration for logging. By default, React will use reportError, or console.error in the older browsers.

React DOM Server

These new APIs are now exported from react-dom/server and have full support for streaming Suspense on the server:

• renderToPipeableStream: for streaming in Node environments.
• renderToReadableStream: for modern edge runtime environments, such as Deno and Cloudflare workers.

The existing renderToString method keeps working but is discouraged.

facebook/react (react-dom)

v18.3.1

Compare Source

v18.3.0

Compare Source

v18.2.0

Compare Source

React DOM

• Provide a component stack as a second argument to onRecoverableError. (@​gnoff in #​24591)
• Fix hydrating into document causing a blank page on mismatch. (@​gnoff in #​24523)
• Fix false positive hydration errors with Suspense. (@​gnoff in #​24480 and @​acdlite in #​24532)
• Fix ignored setState in Safari when adding an iframe. (@​gaearon in #​24459)

React DOM Server

• Pass information about server errors to the client. (@​salazarm and @​gnoff in #​24551 and #​24591)
• Allow to provide a reason when aborting the HTML stream. (@​gnoff in #​24680)
• Eliminate extraneous text separators in the HTML where possible. (@​gnoff in #​24630)
• Disallow complex children inside <title> elements to match the browser constraints. (@​gnoff in #​24679)
• Fix buffering in some worker environments by explicitly setting highWaterMark to 0. (@​jplhomer in #​24641)

Server Components (Experimental)

• Add support for useId() inside Server Components. (@​gnoff in #​24172)

v18.1.0

Compare Source

React DOM

• Fix the false positive warning about react-dom/client when using UMD bundle. (@​alireza-molaee in #​24274)
• Fix suppressHydrationWarning to work in production too. (@​gaearon in #​24271)
• Fix componentWillUnmount firing twice inside of Suspense. (@​acdlite in #​24308)
• Fix some transition updates being ignored. (@​acdlite in #​24353)
• Fix useDeferredValue causing an infinite loop when passed an unmemoized value. (@​acdlite in #​24247)
• Fix throttling of revealing Suspense fallbacks. (@​sunderls in #​24253)
• Fix an inconsistency in whether the props object is the same between renders. (@​Andarist and @​acdlite in #​24421)
• Fix a missing warning about a setState loop in useEffect. (@​gaearon in #​24298)
• Fix a spurious hydration error. (@​gnoff in #​24404)
• Warn when calling setState in useInsertionEffect. (@​gaearon in #​24295)
• Ensure the reason for hydration errors is always displayed. (@​gaearon in #​24276)

React DOM Server

• Fix escaping for the bootstrapScriptContent contents. (@​gnoff in #​24385)
• Significantly improve performance of renderToPipeableStream. (@​gnoff in #​24291)

ESLint Plugin: React Hooks

• Fix false positive errors with a large number of branches. (@​scyron6 in #​24287)
• Don't consider a known dependency stable when the variable is reassigned. (@​afzalsayed96 in #​24343)

Use Subscription

• Replace the implementation with the use-sync-external-store shim. (@​gaearon in #​24289)

v18.0.0

Compare Source

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

New Features

React

• useId is a new hook for generating unique IDs on both the client and server, while avoiding hydration mismatches. It is primarily useful for component libraries integrating with accessibility APIs that require unique IDs. This solves an issue that already exists in React 17 and below, but it’s even more important in React 18 because of how the new streaming server renderer delivers HTML out-of-order.
• startTransition and useTransition let you mark some state updates as not urgent. Other state updates are considered urgent by default. React will allow urgent state updates (for example, updating a text input) to interrupt non-urgent state updates (for example, rendering a list of search results).
• useDeferredValue lets you defer re-rendering a non-urgent part of the tree. It is similar to debouncing, but has a few advantages compared to it. There is no fixed time delay, so React will attempt the deferred render right after the first render is reflected on the screen. The deferred render is interruptible and doesn't block user input.
• useSyncExternalStore is a new hook that allows external stores to support concurrent reads by forcing updates to the store to be synchronous. It removes the need for useEffect when implementing subscriptions to external data sources, and is recommended for any library that integrates with state external to React.
• useInsertionEffect is a new hook that allows CSS-in-JS libraries to address performance issues of injecting styles in render. Unless you’ve already built a CSS-in-JS library we don’t expect you to ever use this. This hook will run after the DOM is mutated, but before layout effects read the new layout. This solves an issue that already exists in React 17 and below, but is even more important in React 18 because React yields to the browser during concurrent rendering, giving it a chance to recalculate layout.

React DOM Client

These new APIs are now exported from react-dom/client:

• createRoot: New method to create a root to render or unmount. Use it instead of ReactDOM.render. New features in React 18 don't work without it.
• hydrateRoot: New method to hydrate a server rendered application. Use it instead of ReactDOM.hydrate in conjunction with the new React DOM Server APIs. New features in React 18 don't work without it.

Both createRoot and hydrateRoot accept a new option called onRecoverableError in case you want to be notified when React recovers from errors during rendering or hydration for logging. By default, React will use reportError, or console.error in the older browsers.

React DOM Server

These new APIs are now exported from react-dom/server and have full support for streaming Suspense on the server:

• renderToPipeableStream: for streaming in Node environments.
• renderToReadableStream: for modern edge runtime environments, such as Deno and Cloudflare workers.

The existing renderToString method keeps working but is discouraged.

---

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about these updates again.

---

• If you want to rebase/retry this PR, check this box

---

This PR was generated by Mend Renovate. View the repository job log.

[renovate]

⚠ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

• any of the package files in this branch needs updating, or
• the branch becomes conflicted, or
• you click the rebase/retry checkbox if found above, or
• you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: package-lock.json

npm ERR! code ERESOLVE
npm ERR! ERESOLVE could not resolve
npm ERR! 
npm ERR! While resolving: @edx/[email protected]
npm ERR! Found: [email protected]
npm ERR! node_modules/react
npm ERR!   react@"^18.0.0" from the root project
npm ERR!   peer react@">=16.x" from @fortawesome/[email protected]
npm ERR!   node_modules/@edx/frontend-component-header/node_modules/@edx/paragon/node_modules/@fortawesome/react-fontawesome
npm ERR!     @fortawesome/react-fontawesome@"^0.1.18" from @edx/[email protected]
npm ERR!     node_modules/@edx/frontend-component-header/node_modules/@edx/paragon
npm ERR!       @edx/paragon@"21.1.10" from @edx/[email protected]
npm ERR!       node_modules/@edx/frontend-component-header
npm ERR!         @edx/frontend-component-header@"^4.6.0" from the root project
npm ERR!   21 more (@fortawesome/react-fontawesome, ...)
npm ERR! 
npm ERR! Could not resolve dependency:
npm ERR! peer react@"^16.9.0 || ^17.0.0" from @edx/[email protected]
npm ERR! node_modules/@edx/frontend-build
npm ERR!   dev @edx/frontend-build@"13.0.14" from the root project
npm ERR!   peer @edx/frontend-build@">= 8.1.0 || ^12.9.0-alpha.1" from @edx/[email protected]
npm ERR!   node_modules/@edx/frontend-platform
npm ERR!     @edx/frontend-platform@"^5.5.4" from the root project
npm ERR!     2 more (@edx/frontend-component-footer, @edx/frontend-component-header)
npm ERR! 
npm ERR! Conflicting peer dependency: [email protected]
npm ERR! node_modules/react
npm ERR!   peer react@"^16.9.0 || ^17.0.0" from @edx/[email protected]
npm ERR!   node_modules/@edx/frontend-build
npm ERR!     dev @edx/frontend-build@"13.0.14" from the root project
npm ERR!     peer @edx/frontend-build@">= 8.1.0 || ^12.9.0-alpha.1" from @edx/[email protected]
npm ERR!     node_modules/@edx/frontend-platform
npm ERR!       @edx/frontend-platform@"^5.5.4" from the root project
npm ERR!       2 more (@edx/frontend-component-footer, @edx/frontend-component-header)
npm ERR! 
npm ERR! Fix the upstream dependency conflict, or retry
npm ERR! this command with --force or --legacy-peer-deps
npm ERR! to accept an incorrect (and potentially broken) dependency resolution.
npm ERR! 
npm ERR! 
npm ERR! For a full report see:
npm ERR! /tmp/renovate/cache/others/npm/_logs/2024-04-14T05_00_21_788Z-eresolve-report.txt

npm ERR! A complete log of this run can be found in: /tmp/renovate/cache/others/npm/_logs/2024-04-14T05_00_21_788Z-debug-0.log

[renovate]

⚠️ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

• any of the package files in this branch needs updating, or
• the branch becomes conflicted, or
• you click the rebase/retry checkbox if found above, or
• you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: package-lock.json

npm error code ERESOLVE
npm error ERESOLVE could not resolve
npm error
npm error While resolving: @edx/[email protected]
npm error Found: [email protected]
npm error node_modules/react
npm error   react@"^18.0.0" from the root project
npm error   peer react@">=16.3" from @fortawesome/[email protected]
npm error   node_modules/@edx/frontend-component-footer/node_modules/@fortawesome/react-fontawesome
npm error     @fortawesome/react-fontawesome@"0.2.0" from @edx/[email protected]
npm error     node_modules/@edx/frontend-component-footer
npm error       @edx/frontend-component-footer@"^12.2.1" from the root project
npm error   22 more (@fortawesome/react-fontawesome, ...)
npm error
npm error Could not resolve dependency:
npm error peer react@"^16.9.0 || ^17.0.0" from @edx/[email protected]
npm error node_modules/@edx/frontend-build
npm error   dev @edx/frontend-build@"13.0.14" from the root project
npm error   peer @edx/frontend-build@">= 8.1.0 || ^12.9.0-alpha.1" from @edx/[email protected]
npm error   node_modules/@edx/frontend-platform
npm error     @edx/frontend-platform@"^5.5.4" from the root project
npm error     2 more (@edx/frontend-component-footer, @edx/frontend-component-header)
npm error
npm error Conflicting peer dependency: [email protected]
npm error node_modules/react
npm error   peer react@"^16.9.0 || ^17.0.0" from @edx/[email protected]
npm error   node_modules/@edx/frontend-build
npm error     dev @edx/frontend-build@"13.0.14" from the root project
npm error     peer @edx/frontend-build@">= 8.1.0 || ^12.9.0-alpha.1" from @edx/[email protected]
npm error     node_modules/@edx/frontend-platform
npm error       @edx/frontend-platform@"^5.5.4" from the root project
npm error       2 more (@edx/frontend-component-footer, @edx/frontend-component-header)
npm error
npm error Fix the upstream dependency conflict, or retry
npm error this command with --force or --legacy-peer-deps
npm error to accept an incorrect (and potentially broken) dependency resolution.
npm error
npm error
npm error For a full report see:
npm error /tmp/renovate/cache/others/npm/_logs/2024-09-20T16_01_19_793Z-eresolve-report.txt
npm error A complete log of this run can be found in: /tmp/renovate/cache/others/npm/_logs/2024-09-20T16_01_19_793Z-debug-0.log