Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

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

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Mar 29, 2022

This PR contains the following updates:

Package Type Update Change OpenSSF
react (source) dependencies major 17.0.2 -> 18.3.1 OpenSSF Scorecard
react-dom (source) dependencies major 17.0.2 -> 18.3.1 OpenSSF Scorecard

Release Notes

facebook/react (react)

v18.3.1

Compare Source

v18.3.0

Compare Source

v18.2.0

Compare Source

React DOM
React DOM Server
Server Components (Experimental)

v18.1.0

Compare Source

React DOM
React DOM Server
ESLint Plugin: React Hooks
Use Subscription

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
React DOM Server
Server Components (Experimental)

v18.1.0

Compare Source

React DOM
React DOM Server
ESLint Plugin: React Hooks
Use Subscription

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: Enabled.

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
Copy link
Contributor Author

renovate bot commented Mar 29, 2022

⚠ 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: @material-ui/[email protected]
npm ERR! Found: [email protected]
npm ERR! node_modules/react
npm ERR!   react@"18.3.1" from the root project
npm ERR!   peer react@">=16.8.0" from @emotion/[email protected]
npm ERR!   node_modules/@emotion/react
npm ERR!     peer @emotion/react@"^11.0.0" from [email protected]
npm ERR!     node_modules/gatsby-plugin-emotion
npm ERR!       gatsby-plugin-emotion@"7.25.0" from the root project
npm ERR!     peer @emotion/react@"^11.4.0" from [email protected]
npm ERR!     node_modules/gatsby-plugin-material-ui
npm ERR!       gatsby-plugin-material-ui@"4.1.0" from the root project
npm ERR!   8 more (@gatsbyjs/reach-router, gatsby, gatsby-link, ...)
npm ERR! 
npm ERR! Could not resolve dependency:
npm ERR! peer react@"^16.8.0 || ^17.0.0" from @material-ui/[email protected]
npm ERR! node_modules/@material-ui/core
npm ERR!   @material-ui/core@"4.12.4" from the root project
npm ERR!   peer @material-ui/core@"^4.0.0" from @material-ui/[email protected]
npm ERR!   node_modules/@material-ui/icons
npm ERR!     @material-ui/icons@"^4.5.1" from @travi/[email protected]
npm ERR!     node_modules/@travi/travi.org-theme-components
npm ERR!       @travi/travi.org-theme-components@"1.2.0" from the root project
npm ERR!   1 more (@travi/travi.org-theme-components)
npm ERR! 
npm ERR! Conflicting peer dependency: [email protected]
npm ERR! node_modules/react
npm ERR!   peer react@"^16.8.0 || ^17.0.0" from @material-ui/[email protected]
npm ERR!   node_modules/@material-ui/core
npm ERR!     @material-ui/core@"4.12.4" from the root project
npm ERR!     peer @material-ui/core@"^4.0.0" from @material-ui/[email protected]
npm ERR!     node_modules/@material-ui/icons
npm ERR!       @material-ui/icons@"^4.5.1" from @travi/[email protected]
npm ERR!       node_modules/@travi/travi.org-theme-components
npm ERR!         @travi/travi.org-theme-components@"1.2.0" from the root project
npm ERR!     1 more (@travi/travi.org-theme-components)
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! See /tmp/renovate/cache/others/npm/eresolve-report.txt for a full report.

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

@renovate renovate bot force-pushed the renovate/major-react-monorepo branch 4 times, most recently from 61c4691 to 0fc095d Compare April 4, 2022 06:43
@renovate renovate bot force-pushed the renovate/major-react-monorepo branch 4 times, most recently from c73ac29 to 001d2f6 Compare April 26, 2022 19:59
@renovate renovate bot force-pushed the renovate/major-react-monorepo branch 6 times, most recently from 07da33f to 7d5b58a Compare May 2, 2022 04:50
@renovate renovate bot force-pushed the renovate/major-react-monorepo branch 7 times, most recently from 9d21d33 to 0e5bc97 Compare May 14, 2022 18:39
@renovate renovate bot force-pushed the renovate/major-react-monorepo branch 4 times, most recently from cdfeb3c to 072ba2b Compare May 23, 2022 04:26
@renovate renovate bot force-pushed the renovate/major-react-monorepo branch 4 times, most recently from d56c72a to cb50b19 Compare May 30, 2022 04:43
@renovate renovate bot force-pushed the renovate/major-react-monorepo branch 2 times, most recently from 3ee550e to c30ef37 Compare January 10, 2023 06:49
@renovate renovate bot force-pushed the renovate/major-react-monorepo branch 4 times, most recently from 4c77436 to dd9ef66 Compare January 19, 2023 08:23
@renovate renovate bot force-pushed the renovate/major-react-monorepo branch 2 times, most recently from d2bfb35 to 3ca7b16 Compare January 30, 2023 07:53
@renovate renovate bot force-pushed the renovate/major-react-monorepo branch 3 times, most recently from 8af77e9 to f98c17a Compare February 14, 2023 09:57
@renovate renovate bot force-pushed the renovate/major-react-monorepo branch 2 times, most recently from a23b6c0 to edd5534 Compare February 23, 2023 17:32
@renovate renovate bot force-pushed the renovate/major-react-monorepo branch from edd5534 to ad63c01 Compare March 16, 2023 00:16
@renovate renovate bot force-pushed the renovate/major-react-monorepo branch 4 times, most recently from f5468d7 to 0c14b9c Compare March 29, 2023 22:38
@renovate renovate bot force-pushed the renovate/major-react-monorepo branch 3 times, most recently from d64049f to 8596985 Compare April 3, 2023 11:42
@renovate renovate bot force-pushed the renovate/major-react-monorepo branch 4 times, most recently from abcaa7e to 881c21e Compare April 15, 2023 07:07
@renovate renovate bot force-pushed the renovate/major-react-monorepo branch 2 times, most recently from 95241fb to 14f5998 Compare April 26, 2024 20:36
@renovate renovate bot force-pushed the renovate/major-react-monorepo branch from 14f5998 to c5593b9 Compare July 22, 2024 20:40
Copy link
Contributor Author

renovate bot commented Jul 22, 2024

⚠️ 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: @material-ui/[email protected]
npm ERR! Found: [email protected]
npm ERR! node_modules/react
npm ERR!   react@"18.3.1" from the root project
npm ERR!   peer react@">=16.8.0" from @emotion/[email protected]
npm ERR!   node_modules/@emotion/react
npm ERR!     peer @emotion/react@"^11.0.0" from [email protected]
npm ERR!     node_modules/gatsby-plugin-emotion
npm ERR!       gatsby-plugin-emotion@"7.25.0" from the root project
npm ERR!     peer @emotion/react@"^11.4.0" from [email protected]
npm ERR!     node_modules/gatsby-plugin-material-ui
npm ERR!       gatsby-plugin-material-ui@"4.1.0" from the root project
npm ERR!   8 more (@gatsbyjs/reach-router, gatsby, gatsby-link, ...)
npm ERR! 
npm ERR! Could not resolve dependency:
npm ERR! peer react@"^16.8.0 || ^17.0.0" from @material-ui/[email protected]
npm ERR! node_modules/@material-ui/core
npm ERR!   @material-ui/core@"4.12.4" from the root project
npm ERR!   peer @material-ui/core@"^4.0.0" from @material-ui/[email protected]
npm ERR!   node_modules/@material-ui/icons
npm ERR!     @material-ui/icons@"^4.5.1" from @travi/[email protected]
npm ERR!     node_modules/@travi/travi.org-theme-components
npm ERR!       @travi/travi.org-theme-components@"1.2.0" from the root project
npm ERR!   1 more (@travi/travi.org-theme-components)
npm ERR! 
npm ERR! Conflicting peer dependency: [email protected]
npm ERR! node_modules/react
npm ERR!   peer react@"^16.8.0 || ^17.0.0" from @material-ui/[email protected]
npm ERR!   node_modules/@material-ui/core
npm ERR!     @material-ui/core@"4.12.4" from the root project
npm ERR!     peer @material-ui/core@"^4.0.0" from @material-ui/[email protected]
npm ERR!     node_modules/@material-ui/icons
npm ERR!       @material-ui/icons@"^4.5.1" from @travi/[email protected]
npm ERR!       node_modules/@travi/travi.org-theme-components
npm ERR!         @travi/travi.org-theme-components@"1.2.0" from the root project
npm ERR!     1 more (@travi/travi.org-theme-components)
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! See /tmp/renovate/cache/others/npm/eresolve-report.txt for a full report.

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

0 participants