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

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

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

Conversation

renovate[bot]
Copy link

@renovate renovate bot commented May 11, 2022

Mend Renovate

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
@types/react (source) 17.0.37 -> 18.3.3 age adoption passing confidence
@types/react-dom (source) 17.0.11 -> 18.3.0 age adoption passing confidence
react (source) 17.0.2 -> 18.3.1 age adoption passing confidence
react-dom (source) 17.0.2 -> 18.3.1 age adoption passing confidence

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

@vercel
Copy link

vercel bot commented May 11, 2022

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name Status Preview Updated
lab-clock-in-admin ❌ Failed (Inspect) Jun 15, 2022 at 0:14AM (UTC)

@renovate
Copy link
Author

renovate bot commented May 21, 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: @testing-library/react@12.1.5
npm ERR! Found: react@18.3.1
npm ERR! node_modules/react
npm ERR!   react@"18.3.1" from the root project
npm ERR!   peer react@">=16.0.0" from @ant-design/icons@4.7.0
npm ERR!   node_modules/@ant-design/icons
npm ERR!     @ant-design/icons@"^4.7.0" from antd@4.20.3
npm ERR!     node_modules/antd
npm ERR!       antd@"^4.20.3" from the root project
npm ERR!   45 more (@ant-design/react-slick, ...)
npm ERR! 
npm ERR! Could not resolve dependency:
npm ERR! peer react@"<18.0.0" from @testing-library/react@12.1.5
npm ERR! node_modules/@testing-library/react
npm ERR!   dev @testing-library/react@"^12.1.5" from the root project
npm ERR! 
npm ERR! Conflicting peer dependency: react@17.0.2
npm ERR! node_modules/react
npm ERR!   peer react@"<18.0.0" from @testing-library/react@12.1.5
npm ERR!   node_modules/@testing-library/react
npm ERR!     dev @testing-library/react@"^12.1.5" from the root project
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-27T02_43_37_963Z-debug-0.log

@renovate renovate bot force-pushed the renovate/major-react-monorepo branch from 9157aba to 9f46a87 Compare June 15, 2022 00:13
@renovate renovate bot changed the title fix(deps): update react monorepo to v18 (major) Update react monorepo to v18 (major) Sep 25, 2022
@renovate
Copy link
Author

renovate bot commented Mar 16, 2023

Edited/Blocked Notification

Renovate will not automatically rebase this PR, because it does not recognize the last commit author and assumes somebody else may have edited the PR.

You can manually request rebase by checking the rebase/retry box above.

Warning: custom changes will be lost.

@renovate renovate bot force-pushed the renovate/major-react-monorepo branch from 9f46a87 to 6c707c1 Compare March 17, 2023 05:50
@renovate renovate bot changed the title Update react monorepo to v18 (major) chore(deps): update react monorepo to v18 (major) Mar 17, 2023
@renovate renovate bot force-pushed the renovate/major-react-monorepo branch 3 times, most recently from 8304d0d to 2d3b57a Compare March 29, 2023 02:40
@renovate renovate bot force-pushed the renovate/major-react-monorepo branch 2 times, most recently from 4c8b244 to dc3af56 Compare April 17, 2023 17:20
@renovate renovate bot force-pushed the renovate/major-react-monorepo branch 2 times, most recently from c79b3b5 to 178cb99 Compare June 1, 2023 19:55
@renovate renovate bot force-pushed the renovate/major-react-monorepo branch 4 times, most recently from 44f83ed to d2dd079 Compare June 12, 2023 22:49
@renovate renovate bot force-pushed the renovate/major-react-monorepo branch 2 times, most recently from dde7ecc to f956c21 Compare June 23, 2023 21:38
@renovate renovate bot force-pushed the renovate/major-react-monorepo branch 2 times, most recently from 7fceb77 to b7202f8 Compare July 13, 2023 18:16
@renovate renovate bot force-pushed the renovate/major-react-monorepo branch 3 times, most recently from 2d5d485 to d860e22 Compare July 31, 2023 21:20
@renovate renovate bot force-pushed the renovate/major-react-monorepo branch from d860e22 to 012decf Compare August 8, 2023 10:44
@renovate renovate bot force-pushed the renovate/major-react-monorepo branch 6 times, most recently from 98aca5c to 4f11db0 Compare March 7, 2024 00:52
@renovate renovate bot force-pushed the renovate/major-react-monorepo branch 4 times, most recently from 9cc7b0a to 140033d Compare March 18, 2024 19:52
@renovate renovate bot force-pushed the renovate/major-react-monorepo branch 6 times, most recently from ab9e04c to a3009e1 Compare March 28, 2024 18:29
@renovate renovate bot force-pushed the renovate/major-react-monorepo branch 3 times, most recently from cad4b64 to f52d111 Compare April 9, 2024 02:37
@renovate renovate bot force-pushed the renovate/major-react-monorepo branch 3 times, most recently from eb4e1f3 to 8cb3272 Compare April 16, 2024 04:36
@renovate renovate bot force-pushed the renovate/major-react-monorepo branch 4 times, most recently from 7c30e2b to 6fc7421 Compare April 27, 2024 02:43
@renovate renovate bot force-pushed the renovate/major-react-monorepo branch from 6fc7421 to 2ca835c Compare May 11, 2024 11:27
Copy link
Author

renovate bot commented May 11, 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: @testing-library/react@12.1.5
npm ERR! Found: react@18.3.1
npm ERR! node_modules/react
npm ERR!   react@"18.3.1" from the root project
npm ERR!   peer react@">=16.0.0" from @ant-design/icons@4.7.0
npm ERR!   node_modules/@ant-design/icons
npm ERR!     @ant-design/icons@"^4.7.0" from antd@4.20.3
npm ERR!     node_modules/antd
npm ERR!       antd@"^4.20.3" from the root project
npm ERR!   45 more (@ant-design/react-slick, ...)
npm ERR! 
npm ERR! Could not resolve dependency:
npm ERR! peer react@"<18.0.0" from @testing-library/react@12.1.5
npm ERR! node_modules/@testing-library/react
npm ERR!   dev @testing-library/react@"^12.1.5" from the root project
npm ERR! 
npm ERR! Conflicting peer dependency: react@17.0.2
npm ERR! node_modules/react
npm ERR!   peer react@"<18.0.0" from @testing-library/react@12.1.5
npm ERR!   node_modules/@testing-library/react
npm ERR!     dev @testing-library/react@"^12.1.5" from the root project
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-05-23T21_53_07_239Z-debug-0.log

@renovate renovate bot force-pushed the renovate/major-react-monorepo branch from 2ca835c to 361790f Compare May 23, 2024 21:53
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.

None yet

0 participants