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

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

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Dec 19, 2022

Mend Renovate

This PR contains the following updates:

Package Change 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) 17.0.2 -> 18.3.1 age adoption passing confidence
react-dom (source) ^16.9.0 || ^17.0.0 -> ^16.9.0 || ^17.0.0 || ^18.0.0 age adoption passing confidence
react-dom (source) 17.0.2 -> 18.3.1 age adoption passing confidence
react-test-renderer (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.

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.


Configuration

📅 Schedule: Branch creation - "before 4am on Monday" in timezone America/New_York, 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 has been generated by Mend Renovate. View repository job log here.

@renovate
Copy link
Contributor Author

renovate bot commented Dec 19, 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 error code ERESOLVE
npm error ERESOLVE could not resolve
npm error
npm error While resolving: @edx/frontend-enterprise-utils@9.1.0
npm error Found: react@18.3.1
npm error node_modules/react
npm error   dev react@"18.3.1" from the root project
npm error   peer react@"*" from @testing-library/react@12.1.4
npm error   node_modules/@edx/frontend-enterprise-utils/node_modules/@testing-library/react
npm error     @testing-library/react@"12.1.4" from @edx/frontend-enterprise-utils@9.1.0
npm error     node_modules/@edx/frontend-enterprise-utils
npm error       @edx/frontend-enterprise-utils@"9.1.0" from the root project
npm error   34 more (@fortawesome/react-fontawesome, ...)
npm error
npm error Could not resolve dependency:
npm error peer react@"^16.12.0 || ^17.0.0" from @edx/frontend-enterprise-utils@9.1.0
npm error node_modules/@edx/frontend-enterprise-utils
npm error   @edx/frontend-enterprise-utils@"9.1.0" from the root project
npm error
npm error Conflicting peer dependency: react@17.0.2
npm error node_modules/react
npm error   peer react@"^16.12.0 || ^17.0.0" from @edx/frontend-enterprise-utils@9.1.0
npm error   node_modules/@edx/frontend-enterprise-utils
npm error     @edx/frontend-enterprise-utils@"9.1.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-05-08T06_30_01_333Z-eresolve-report.txt

npm error A complete log of this run can be found in: /tmp/renovate/cache/others/npm/_logs/2024-05-08T06_30_01_333Z-debug-0.log

@renovate renovate bot force-pushed the renovate/major-react-monorepo branch 4 times, most recently from 3cc98f3 to 7a51102 Compare December 26, 2022 08:48
@renovate renovate bot force-pushed the renovate/major-react-monorepo branch 2 times, most recently from 4f5583d to 29f6331 Compare January 9, 2023 10:02
@renovate renovate bot force-pushed the renovate/major-react-monorepo branch 3 times, most recently from 6b2ada0 to 50c8538 Compare January 30, 2023 09:37
@renovate renovate bot force-pushed the renovate/major-react-monorepo branch 7 times, most recently from f9a7174 to f325b52 Compare February 7, 2023 05:45
@renovate renovate bot force-pushed the renovate/major-react-monorepo branch 4 times, most recently from 413fd49 to 7ad7d65 Compare February 20, 2023 12:03
@renovate renovate bot force-pushed the renovate/major-react-monorepo branch 4 times, most recently from 22a857a to 2f7e5ce Compare March 8, 2023 00:09
@renovate renovate bot force-pushed the renovate/major-react-monorepo branch 2 times, most recently from e0645d7 to 4a77814 Compare March 20, 2023 09:15
@renovate renovate bot force-pushed the renovate/major-react-monorepo branch 3 times, most recently from 70ee500 to 79e71d2 Compare March 27, 2023 06:37
@renovate renovate bot force-pushed the renovate/major-react-monorepo branch 3 times, most recently from 8462d9c to 2bb2af3 Compare January 22, 2024 13:25
@renovate renovate bot force-pushed the renovate/major-react-monorepo branch from 2bb2af3 to 1ce5c96 Compare January 28, 2024 19:48
@renovate renovate bot force-pushed the renovate/major-react-monorepo branch 3 times, most recently from bcfeb77 to 5e69c20 Compare February 6, 2024 09:29
@renovate renovate bot force-pushed the renovate/major-react-monorepo branch 5 times, most recently from fc33a1a to 8237875 Compare February 19, 2024 14:03
@renovate renovate bot force-pushed the renovate/major-react-monorepo branch from 8237875 to 09bd9e0 Compare February 27, 2024 11:21
@renovate renovate bot force-pushed the renovate/major-react-monorepo branch 2 times, most recently from 44b690a to 8789334 Compare March 20, 2024 06:40
@renovate renovate bot force-pushed the renovate/major-react-monorepo branch 2 times, most recently from 6df870f to 8a4ae51 Compare April 5, 2024 09:35
@renovate renovate bot force-pushed the renovate/major-react-monorepo branch 3 times, most recently from fe41cd3 to ca2dcb1 Compare April 15, 2024 22:04
@renovate renovate bot force-pushed the renovate/major-react-monorepo branch 5 times, most recently from 45bd9bb to 34b87b6 Compare April 26, 2024 19:20
@renovate renovate bot force-pushed the renovate/major-react-monorepo branch 3 times, most recently from 9305d9f to c44b322 Compare May 6, 2024 12:10
@renovate renovate bot force-pushed the renovate/major-react-monorepo branch from c44b322 to d79ebc4 Compare May 8, 2024 06:30
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