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) #309

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

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Feb 24, 2023

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
@types/react (source) ^17.0.0 -> ^18.0.0 age adoption passing confidence
@types/react-dom (source) ^17.0.11 -> ^18.0.0 age adoption passing confidence
react (source) ^16.9.0 || ^17.0.0 -> ^16.9.0 || ^17.0.0 || ^18.0.0 age adoption passing confidence
react (source) 16.14.0 -> 18.3.1 age adoption passing confidence
react-dom (source) 16.14.0 -> 18.3.1 age adoption passing confidence
react-test-renderer (source) 16.14.0 -> 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.

v17.0.2

Compare Source

React DOM

v17.0.1

Compare Source

React DOM

v17.0.0

Compare Source

Today, we are releasing React 17!

Learn more about React 17 and how to update to it on the official React blog.

React
React DOM
React DOM Server
React Test Renderer
Concurrent Mode (Experimental)
facebook/react (react-test-renderer)

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.

v17.0.2

Compare Source

React DOM

v17.0.1

Compare Source

React DOM

v17.0.0

Compare Source

Today, we are releasing React 17!

Learn more about React 17 and how to update to it on the official React blog.

React
React DOM

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 renovate bot force-pushed the renovate/major-react-monorepo branch from f80abf3 to 54cd0a2 Compare February 28, 2023 04:42
@renovate renovate bot force-pushed the renovate/major-react-monorepo branch from 54cd0a2 to 1be8511 Compare March 8, 2023 07:38
@renovate renovate bot force-pushed the renovate/major-react-monorepo branch from 1be8511 to b95b893 Compare March 15, 2023 12:16
@renovate renovate bot force-pushed the renovate/major-react-monorepo branch 2 times, most recently from cf65056 to 6d9d6a4 Compare March 24, 2023 11:28
@renovate renovate bot force-pushed the renovate/major-react-monorepo branch 7 times, most recently from 1f5890c to 1ecdccf Compare April 5, 2023 12:49
@renovate renovate bot force-pushed the renovate/major-react-monorepo branch 6 times, most recently from 8069b04 to 910c1f3 Compare April 14, 2023 08:20
@renovate renovate bot force-pushed the renovate/major-react-monorepo branch 6 times, most recently from dc71f3b to c8a6385 Compare April 26, 2023 02:39
@renovate renovate bot force-pushed the renovate/major-react-monorepo branch 6 times, most recently from a1d096d to 7783b81 Compare May 4, 2023 17:16
@renovate renovate bot force-pushed the renovate/major-react-monorepo branch from ef711f3 to 567f2f5 Compare May 15, 2024 13:28
@renovate renovate bot force-pushed the renovate/major-react-monorepo branch 7 times, most recently from 055b6c0 to 8fcd073 Compare June 17, 2024 15:01
@renovate renovate bot force-pushed the renovate/major-react-monorepo branch from 8fcd073 to a8b966f Compare June 21, 2024 13:06
@renovate renovate bot force-pushed the renovate/major-react-monorepo branch from a8b966f to 3b2b13e Compare July 10, 2024 22:26
@renovate renovate bot force-pushed the renovate/major-react-monorepo branch 6 times, most recently from 6d45eb9 to 477f923 Compare July 23, 2024 21:09
@renovate renovate bot force-pushed the renovate/major-react-monorepo branch 2 times, most recently from 33faca3 to ba63f9a Compare August 13, 2024 21:24
@renovate renovate bot force-pushed the renovate/major-react-monorepo branch from ba63f9a to 32622e6 Compare August 30, 2024 19:08
Copy link
Contributor Author

renovate bot commented Aug 30, 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: example/package-lock.json
npm error code ERESOLVE
npm error ERESOLVE could not resolve
npm error
npm error While resolving: @openedx/[email protected]
npm error Found: [email protected]
npm error node_modules/react
npm error   react@"18.3.1" from the root project
npm error   peer react@">=16.x" from @fortawesome/[email protected]
npm error   node_modules/@fortawesome/react-fontawesome
npm error     @fortawesome/react-fontawesome@"^0.1.18" from @openedx/[email protected]
npm error     node_modules/@openedx/paragon
npm error       @openedx/paragon@"22.7.0" from the root project
npm error   25 more (@restart/context, @restart/hooks, prop-types-extra, ...)
npm error
npm error Could not resolve dependency:
npm error peer react@"^16.8.6 || ^17.0.0" from @openedx/[email protected]
npm error node_modules/@openedx/paragon
npm error   @openedx/paragon@"22.7.0" from the root project
npm error
npm error Conflicting peer dependency: [email protected]
npm error node_modules/react
npm error   peer react@"^16.8.6 || ^17.0.0" from @openedx/[email protected]
npm error   node_modules/@openedx/paragon
npm error     @openedx/paragon@"22.7.0" from the root project
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-11-18T17_46_26_615Z-eresolve-report.txt
npm error A complete log of this run can be found in: /tmp/renovate/cache/others/npm/_logs/2024-11-18T17_46_26_615Z-debug-0.log

@renovate renovate bot force-pushed the renovate/major-react-monorepo branch from 32622e6 to ad0b33c Compare September 6, 2024 18:15
@renovate renovate bot force-pushed the renovate/major-react-monorepo branch 4 times, most recently from 9b761fc to b507c77 Compare September 19, 2024 22:04
@renovate renovate bot force-pushed the renovate/major-react-monorepo branch from b507c77 to 741ad60 Compare September 25, 2024 17:45
@renovate renovate bot force-pushed the renovate/major-react-monorepo branch from 741ad60 to 2f43ebd Compare October 31, 2024 20:03
@renovate renovate bot force-pushed the renovate/major-react-monorepo branch from 2f43ebd to bd9967e Compare November 8, 2024 17:13
@renovate renovate bot force-pushed the renovate/major-react-monorepo branch from bd9967e to cea30b5 Compare November 18, 2024 17:46
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