Skip to content
This repository has been archived by the owner on Mar 27, 2024. It is now read-only.

chore(deps): update react monorepo to v18 (major) #242

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

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Mar 30, 2022

Mend Renovate

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
react (source) 17.0.2 -> 18.2.0 age adoption passing confidence
react-dom (source) 17.0.2 -> 18.2.0 age adoption passing confidence

Release Notes

facebook/react (react)

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 - "after 10pm every weekday,before 5am every weekday,every weekend" (UTC), Automerge - At any time (no schedule defined).

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

Rebasing: Whenever PR becomes conflicted, 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 has been generated by Mend Renovate. View repository job log here.

@renovate
Copy link
Contributor Author

renovate bot commented Mar 30, 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 WARN ERESOLVE overriding peer dependency
npm WARN While resolving: @gatsbyjs/[email protected]
npm WARN Found: [email protected]
npm WARN node_modules/react
npm WARN   dev react@"18.2.0" from the root project
npm WARN   2 more (react-syntax-highlighter, react-dom)
npm WARN 
npm WARN Could not resolve dependency:
npm WARN peer react@"15.x || 16.x || 17.x" from @gatsbyjs/[email protected]
npm WARN node_modules/@gatsbyjs/reach-router
npm WARN   @gatsbyjs/reach-router@"^1.3.6" from [email protected]
npm WARN   node_modules/gatsby
npm WARN   2 more (gatsby-link, gatsby-react-router-scroll)
npm WARN 
npm WARN Conflicting peer dependency: [email protected]
npm WARN node_modules/react
npm WARN   peer react@"15.x || 16.x || 17.x" from @gatsbyjs/[email protected]
npm WARN   node_modules/@gatsbyjs/reach-router
npm WARN     @gatsbyjs/reach-router@"^1.3.6" from [email protected]
npm WARN     node_modules/gatsby
npm WARN     2 more (gatsby-link, gatsby-react-router-scroll)
npm WARN ERESOLVE overriding peer dependency
npm WARN While resolving: @gatsbyjs/[email protected]
npm WARN Found: [email protected]
npm WARN node_modules/react-dom
npm WARN   dev react-dom@"18.2.0" from the root project
npm WARN 
npm WARN Could not resolve dependency:
npm WARN peer react-dom@"15.x || 16.x || 17.x" from @gatsbyjs/[email protected]
npm WARN node_modules/@gatsbyjs/reach-router
npm WARN   @gatsbyjs/reach-router@"^1.3.6" from [email protected]
npm WARN   node_modules/gatsby
npm WARN   2 more (gatsby-link, gatsby-react-router-scroll)
npm WARN 
npm WARN Conflicting peer dependency: [email protected]
npm WARN node_modules/react-dom
npm WARN   peer react-dom@"15.x || 16.x || 17.x" from @gatsbyjs/[email protected]
npm WARN   node_modules/@gatsbyjs/reach-router
npm WARN     @gatsbyjs/reach-router@"^1.3.6" from [email protected]
npm WARN     node_modules/gatsby
npm WARN     2 more (gatsby-link, gatsby-react-router-scroll)
npm ERR! code ERESOLVE
npm ERR! ERESOLVE could not resolve
npm ERR! 
npm ERR! While resolving: [email protected]
npm ERR! Found: [email protected]
npm ERR! node_modules/react
npm ERR!   dev react@"18.2.0" from the root project
npm ERR!   peer react@">= 0.14.0" from [email protected]
npm ERR!   node_modules/react-syntax-highlighter
npm ERR!     dev react-syntax-highlighter@"15.5.0" from the root project
npm ERR!   1 more (react-dom)
npm ERR! 
npm ERR! Could not resolve dependency:
npm ERR! peer react@"^16.9.0 || ^17.0.0" from [email protected]
npm ERR! node_modules/gatsby
npm ERR!   dev gatsby@"3.15.0" from the root project
npm ERR!   peer gatsby@"^3.0.0-next.0" from [email protected]
npm ERR!   node_modules/babel-plugin-remove-graphql-queries
npm ERR!     babel-plugin-remove-graphql-queries@"^3.15.0" from [email protected]
npm ERR!     1 more (gatsby-plugin-typescript)
npm ERR!   4 more (gatsby-plugin-catch-links, ...)
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 [email protected]
npm ERR!   node_modules/gatsby
npm ERR!     dev gatsby@"3.15.0" from the root project
npm ERR!     peer gatsby@"^3.0.0-next.0" from [email protected]
npm ERR!     node_modules/babel-plugin-remove-graphql-queries
npm ERR!       babel-plugin-remove-graphql-queries@"^3.15.0" from [email protected]
npm ERR!       1 more (gatsby-plugin-typescript)
npm ERR!     4 more (gatsby-plugin-catch-links, ...)
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/2023-02-14T08_29_35_072Z-debug-0.log

@renovate renovate bot force-pushed the renovate/major-react-monorepo branch from c07e831 to 39a5c2a Compare April 12, 2022 00:40
@renovate renovate bot force-pushed the renovate/major-react-monorepo branch 2 times, most recently from 3458c90 to 7436ac9 Compare April 27, 2022 00:00
@renovate renovate bot force-pushed the renovate/major-react-monorepo branch from 7436ac9 to 7b53415 Compare May 10, 2022 02:28
@renovate renovate bot force-pushed the renovate/major-react-monorepo branch from 7b53415 to 309a0ea Compare May 24, 2022 02:19
@renovate renovate bot force-pushed the renovate/major-react-monorepo branch 2 times, most recently from 8a0d5f2 to 219ac23 Compare June 14, 2022 22:09
@renovate renovate bot force-pushed the renovate/major-react-monorepo branch 2 times, most recently from 40825e3 to a2fce60 Compare June 29, 2022 02:16
@renovate renovate bot force-pushed the renovate/major-react-monorepo branch from a2fce60 to 3401630 Compare July 20, 2022 01:28
@renovate renovate bot force-pushed the renovate/major-react-monorepo branch from 3401630 to 80a25aa Compare August 3, 2022 03:48
@renovate renovate bot force-pushed the renovate/major-react-monorepo branch 2 times, most recently from 79e9888 to 597bbf6 Compare August 17, 2022 00:54
@renovate renovate bot force-pushed the renovate/major-react-monorepo branch from 597bbf6 to ed7dedb Compare August 31, 2022 03:21
@renovate renovate bot force-pushed the renovate/major-react-monorepo branch from ed7dedb to 02b4891 Compare September 14, 2022 03:04
@renovate renovate bot force-pushed the renovate/major-react-monorepo branch from 02b4891 to 6934688 Compare September 28, 2022 03:46
@renovate renovate bot force-pushed the renovate/major-react-monorepo branch 2 times, most recently from 4b4574c to 4f5439e Compare October 12, 2022 03:23
@renovate renovate bot force-pushed the renovate/major-react-monorepo branch from 4f5439e to 30d346c Compare October 26, 2022 03:39
@renovate renovate bot force-pushed the renovate/major-react-monorepo branch 4 times, most recently from 117626e to 5490861 Compare December 10, 2022 02:22
@renovate renovate bot changed the title chore(deps): update react monorepo to v18 (major) Update react monorepo to v18 (major) Dec 17, 2022
@renovate renovate bot changed the title Update react monorepo to v18 (major) chore(deps): update react monorepo to v18 (major) Dec 17, 2022
@renovate renovate bot force-pushed the renovate/major-react-monorepo branch from 5490861 to 1a062bb Compare January 24, 2023 03:26
@renovate renovate bot force-pushed the renovate/major-react-monorepo branch from 1a062bb to 1ed16de Compare February 14, 2023 08:29
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

0 participants