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.

Sign up for GitHub

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

Jump to bottom

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

Closed
wants to merge 1 commit into from
Closed

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

wants to merge 1 commit into from

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Mar 6, 2023 •
edited
Loading

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) 16.14.0 -> 18.2.0 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) 16.14.0 -> 18.2.0 age adoption passing confidence

Release Notes

facebook/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.

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)

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 Mar 6, 2023 •
edited
Loading

⚠ 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: @edx/[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@">=16.x" from @fortawesome/[email protected]
npm ERR!   node_modules/@fortawesome/react-fontawesome
npm ERR!     @fortawesome/react-fontawesome@"^0.1.18" from @edx/[email protected]
npm ERR!     node_modules/@edx/paragon
npm ERR!       dev @edx/paragon@"^20.30.1" from the root project
npm ERR!   26 more (@restart/context, @restart/hooks, prop-types-extra, ...)
npm ERR! 
npm ERR! Could not resolve dependency:
npm ERR! peer react@"^16.9.0 || ^17.0.0" from @edx/[email protected]
npm ERR! node_modules/@edx/frontend-build
npm ERR!   dev @edx/frontend-build@"12.8.51" from the root project
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 @edx/[email protected]
npm ERR!   node_modules/@edx/frontend-build
npm ERR!     dev @edx/frontend-build@"12.8.51" 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! 
npm ERR! For a full report see:
npm ERR! /tmp/worker/43f1f6/ab8f14/cache/others/npm/_logs/2023-06-22T09_14_03_127Z-eresolve-report.txt

npm ERR! A complete log of this run can be found in: /tmp/worker/43f1f6/ab8f14/cache/others/npm/_logs/2023-06-22T09_14_03_127Z-debug-0.log

@renovate renovate bot force-pushed the renovate/major-react-monorepo branch 2 times, most recently from c51a901 to f949c36 Compare March 9, 2023 15:48
@renovate renovate bot force-pushed the renovate/major-react-monorepo branch 4 times, most recently from 4c8e949 to bf443bd Compare March 20, 2023 11:53
@renovate renovate bot force-pushed the renovate/major-react-monorepo branch 7 times, most recently from 91b11b8 to 753e90c Compare March 31, 2023 09:46
@renovate renovate bot force-pushed the renovate/major-react-monorepo branch 4 times, most recently from c83ea73 to c6ff095 Compare April 11, 2023 13:54
@renovate renovate bot force-pushed the renovate/major-react-monorepo branch 6 times, most recently from f0307c9 to e1c37c6 Compare April 19, 2023 21:47
@renovate renovate bot force-pushed the renovate/major-react-monorepo branch 5 times, most recently from c210adf to 692bb17 Compare May 8, 2023 13:15
@renovate renovate bot force-pushed the renovate/major-react-monorepo branch from 692bb17 to afa4b47 Compare May 10, 2023 21:29
@renovate renovate bot force-pushed the renovate/major-react-monorepo branch 2 times, most recently from 11c0e82 to 0f40fe8 Compare May 22, 2023 19:24
@renovate renovate bot force-pushed the renovate/major-react-monorepo branch 7 times, most recently from e1a96c3 to 7fb9850 Compare May 30, 2023 06:44
@renovate renovate bot force-pushed the renovate/major-react-monorepo branch from 7fb9850 to 8954399 Compare June 5, 2023 08:04
@renovate renovate bot force-pushed the renovate/major-react-monorepo branch from 8954399 to e318633 Compare June 12, 2023 09:56
@renovate renovate bot force-pushed the renovate/major-react-monorepo branch from e318633 to 4e2b935 Compare June 12, 2023 13:42
@abdullahwaheed
Copy link
Contributor

we will incrementally upgrade react, so closing this PR

@renovate
Copy link
Contributor Author

renovate bot commented Jun 22, 2023 •
edited
Loading

Renovate Ignore Notification

Because you closed this PR without merging, Renovate will ignore this update. You will not get PRs for any future 18.x releases. But if you manually upgrade to 18.x then Renovate will re-enable minor and patch updates automatically.

If you accidentally closed this PR, or if you changed your mind: rename this PR to get a fresh replacement PR.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers
No reviews
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
1 participant
@abdullahwaheed