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

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

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented May 15, 2023

Mend Renovate

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
@types/react (source) 17.0.80 -> 18.3.3 age adoption passing confidence
@types/react-dom (source) 17.0.25 -> 18.3.0 age adoption passing confidence
react (source) 17.0.2 -> 18.3.1 age adoption passing confidence
react (source) 17.x -> 18.x age adoption passing confidence
react-dom (source) 17.0.2 -> 18.3.1 age adoption passing confidence
react-dom (source) 17.x -> 18.x age adoption passing confidence
react-is (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-is)

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" (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 renovate bot added the 🤖 Type: Dependencies Dependency updates or something similar label May 15, 2023
@changeset-bot
Copy link

changeset-bot bot commented May 15, 2023

⚠️ No Changeset found

Latest commit: 2eed7f5

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

@vercel
Copy link

vercel bot commented May 15, 2023

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

Name Status Preview Comments Updated (UTC)
ui-kit ✅ Ready (Inspect) Visit Preview 💬 Add feedback Jun 26, 2024 9:07am

@renovate renovate bot force-pushed the renovate/major-react-monorepo branch from ddc83b0 to ac2e9d4 Compare May 15, 2023 17:24
@renovate renovate bot force-pushed the renovate/major-react-monorepo branch from ac2e9d4 to 511f3e9 Compare May 16, 2023 17:23
@renovate renovate bot force-pushed the renovate/major-react-monorepo branch from 511f3e9 to 2a85456 Compare May 17, 2023 08:36
@renovate renovate bot force-pushed the renovate/major-react-monorepo branch from 2a85456 to 049b01c Compare May 17, 2023 08:55
@renovate renovate bot force-pushed the renovate/major-react-monorepo branch from 049b01c to feceac2 Compare May 19, 2023 19:38
@renovate renovate bot force-pushed the renovate/major-react-monorepo branch from feceac2 to b360c6c Compare May 19, 2023 20:08
@renovate renovate bot force-pushed the renovate/major-react-monorepo branch from b360c6c to d9d0fc4 Compare May 23, 2023 17:59
@renovate renovate bot force-pushed the renovate/major-react-monorepo branch from d9d0fc4 to 33fa6d3 Compare May 24, 2023 15:59
@renovate renovate bot force-pushed the renovate/major-react-monorepo branch from 33fa6d3 to db7137d Compare May 30, 2023 08:45
@renovate renovate bot force-pushed the renovate/major-react-monorepo branch from db7137d to 60abd97 Compare May 31, 2023 07:53
@renovate renovate bot force-pushed the renovate/major-react-monorepo branch from 60abd97 to 03b499f Compare June 2, 2023 10:52
@renovate renovate bot force-pushed the renovate/major-react-monorepo branch from 03b499f to 61c643f Compare June 2, 2023 12:25
@renovate renovate bot force-pushed the renovate/major-react-monorepo branch from 61c643f to 0ec21f5 Compare June 6, 2023 07:08
Copy link

gitstream-cm bot commented Jun 17, 2024

This PR is missing a Jira ticket reference in the title or description.
Please add a Jira ticket reference to the title or description of this PR.

Copy link

gitstream-cm bot commented Jun 17, 2024

🥷 Code experts: emmenko

emmenko has most 🧠 knowledge in the files.

See details

design-system/package.json

Knowledge based on git-blame:
emmenko: 57%

docs/package.json

Knowledge based on git-blame:
emmenko: 58%

docs/yarn.lock

Knowledge based on git-blame:
emmenko: 75%

package.json

Knowledge based on git-blame:
emmenko: 37%

packages/calendar-utils/package.json

Knowledge based on git-blame:
emmenko: 46%

packages/components/accessible-hidden/package.json

Knowledge based on git-blame:
emmenko: 45%

packages/components/avatar/package.json

Knowledge based on git-blame:
emmenko: 57%

packages/components/buttons/accessible-button/package.json

Knowledge based on git-blame:
emmenko: 54%

packages/components/buttons/flat-button/package.json

Knowledge based on git-blame:
emmenko: 54%

packages/components/buttons/icon-button/package.json

Knowledge based on git-blame:
emmenko: 51%

packages/components/buttons/link-button/package.json

Knowledge based on git-blame:
emmenko: 48%

packages/components/buttons/primary-button/package.json

Knowledge based on git-blame:
emmenko: 51%

packages/components/buttons/secondary-button/package.json

Knowledge based on git-blame:
emmenko: 48%

packages/components/buttons/secondary-icon-button/package.json

Knowledge based on git-blame:
emmenko: 51%

packages/components/card/package.json

Knowledge based on git-blame:
emmenko: 50%

packages/components/collapsible-motion/package.json

Knowledge based on git-blame:
emmenko: 57%

packages/components/collapsible-panel/package.json

Knowledge based on git-blame:
emmenko: 49%

packages/components/collapsible/package.json

Knowledge based on git-blame:
emmenko: 57%

packages/components/constraints/package.json

Knowledge based on git-blame:
emmenko: 54%

packages/components/data-table-manager/package.json

Knowledge based on git-blame:
emmenko: 33%

packages/components/data-table/package.json

Knowledge based on git-blame:
emmenko: 42%

packages/components/dropdowns/dropdown-menu/package.json

Knowledge based on git-blame:

packages/components/field-errors/package.json

Knowledge based on git-blame:
emmenko: 62%

packages/components/field-label/package.json

Knowledge based on git-blame:
emmenko: 49%

packages/components/field-warnings/package.json

Knowledge based on git-blame:

packages/components/fields/async-creatable-select-field/package.json

Knowledge based on git-blame:
emmenko: 49%

packages/components/fields/async-select-field/package.json

Knowledge based on git-blame:
emmenko: 49%

packages/components/fields/creatable-select-field/package.json

Knowledge based on git-blame:
emmenko: 49%

packages/components/fields/date-field/package.json

Knowledge based on git-blame:
emmenko: 49%

packages/components/fields/date-range-field/package.json

Knowledge based on git-blame:
emmenko: 49%

packages/components/fields/date-time-field/package.json

Knowledge based on git-blame:
emmenko: 49%

packages/components/fields/localized-multiline-text-field/package.json

Knowledge based on git-blame:
emmenko: 49%

packages/components/fields/localized-text-field/package.json

Knowledge based on git-blame:
emmenko: 49%

packages/components/fields/money-field/package.json

Knowledge based on git-blame:
emmenko: 48%

packages/components/fields/multiline-text-field/package.json

Knowledge based on git-blame:
emmenko: 49%

packages/components/fields/number-field/package.json

Knowledge based on git-blame:
emmenko: 49%

packages/components/fields/password-field/package.json

Knowledge based on git-blame:
emmenko: 48%

packages/components/fields/radio-field/package.json

Knowledge based on git-blame:
emmenko: 49%

packages/components/fields/search-select-field/package.json

Knowledge based on git-blame:
emmenko: 36%

packages/components/fields/select-field/package.json

Knowledge based on git-blame:
emmenko: 49%

packages/components/fields/text-field/package.json

Knowledge based on git-blame:
emmenko: 49%

packages/components/fields/time-field/package.json

Knowledge based on git-blame:
emmenko: 49%

packages/components/grid/package.json

Knowledge based on git-blame:
emmenko: 62%

packages/components/icons/package.json

Knowledge based on git-blame:
emmenko: 48%

packages/components/inputs/async-creatable-select-input/package.json

Knowledge based on git-blame:
emmenko: 43%

packages/components/inputs/async-select-input/package.json

Knowledge based on git-blame:
emmenko: 46%

packages/components/inputs/checkbox-input/package.json

Knowledge based on git-blame:
emmenko: 51%

packages/components/inputs/creatable-select-input/package.json

Knowledge based on git-blame:
emmenko: 45%

packages/components/inputs/date-input/package.json

Knowledge based on git-blame:
emmenko: 37%

packages/components/inputs/date-range-input/package.json

Knowledge based on git-blame:
emmenko: 37%

packages/components/inputs/date-time-input/package.json

Knowledge based on git-blame:
emmenko: 37%

packages/components/inputs/input-utils/package.json

Knowledge based on git-blame:
emmenko: 68%

packages/components/inputs/localized-money-input/package.json

Knowledge based on git-blame:
emmenko: 42%

packages/components/inputs/localized-multiline-text-input/package.json

Knowledge based on git-blame:
emmenko: 41%

packages/components/inputs/localized-rich-text-input/package.json

Knowledge based on git-blame:
emmenko: 38%

packages/components/inputs/localized-text-input/package.json

Knowledge based on git-blame:
emmenko: 48%

packages/components/inputs/money-input/package.json

Knowledge based on git-blame:
emmenko: 44%

packages/components/inputs/multiline-text-input/package.json

Knowledge based on git-blame:
emmenko: 45%

packages/components/inputs/number-input/package.json

Knowledge based on git-blame:
emmenko: 53%

packages/components/inputs/password-input/package.json

Knowledge based on git-blame:
emmenko: 55%

packages/components/inputs/radio-input/package.json

Knowledge based on git-blame:
emmenko: 51%

packages/components/inputs/rich-text-input/package.json

Knowledge based on git-blame:
emmenko: 40%

packages/components/inputs/rich-text-utils/package.json

Knowledge based on git-blame:
emmenko: 53%

packages/components/inputs/search-select-input/package.json

Knowledge based on git-blame:
emmenko: 41%

packages/components/inputs/search-text-input/package.json

Knowledge based on git-blame:
emmenko: 10%

packages/components/inputs/select-input/package.json

Knowledge based on git-blame:
emmenko: 48%

packages/components/inputs/select-utils/package.json

Knowledge based on git-blame:
emmenko: 50%

packages/components/inputs/selectable-search-input/package.json

Knowledge based on git-blame:
emmenko: 4%

packages/components/inputs/text-input/package.json

Knowledge based on git-blame:
emmenko: 53%

packages/components/inputs/time-input/package.json

Knowledge based on git-blame:
emmenko: 53%

packages/components/inputs/toggle-input/package.json

Knowledge based on git-blame:
emmenko: 53%

packages/components/label/package.json

Knowledge based on git-blame:
emmenko: 59%

packages/components/link/package.json

Knowledge based on git-blame:
emmenko: 56%

packages/components/loading-spinner/package.json

Knowledge based on git-blame:
emmenko: 53%

packages/components/messages/package.json

Knowledge based on git-blame:
emmenko: 59%

packages/components/notifications/package.json

Knowledge based on git-blame:
emmenko: 57%

packages/components/pagination/package.json

Knowledge based on git-blame:
emmenko: 17%

packages/components/primary-action-dropdown/package.json

Knowledge based on git-blame:
emmenko: 48%

packages/components/progress-bar/package.json

Knowledge based on git-blame:

packages/components/spacings/spacings-inline/package.json

Knowledge based on git-blame:
emmenko: 60%

packages/components/spacings/spacings-inset-squish/package.json

Knowledge based on git-blame:
emmenko: 60%

packages/components/spacings/spacings-inset/package.json

Knowledge based on git-blame:
emmenko: 60%

packages/components/spacings/spacings-stack/package.json

Knowledge based on git-blame:
emmenko: 60%

packages/components/stamp/package.json

Knowledge based on git-blame:
emmenko: 51%

packages/components/tag/package.json

Knowledge based on git-blame:
emmenko: 52%

packages/components/text/package.json

Knowledge based on git-blame:
emmenko: 56%

packages/components/tooltip/package.json

Knowledge based on git-blame:
emmenko: 51%

packages/components/view-switcher/package.json

Knowledge based on git-blame:
emmenko: 11%

packages/hooks/package.json

Knowledge based on git-blame:
emmenko: 51%

packages/utils/package.json

Knowledge based on git-blame:
emmenko: 56%

presets/buttons/package.json

Knowledge based on git-blame:
emmenko: 42%

presets/fields/package.json

Knowledge based on git-blame:
emmenko: 31%

presets/inputs/package.json

Knowledge based on git-blame:
emmenko: 25%

presets/spacings/package.json

Knowledge based on git-blame:
emmenko: 54%

presets/ui-kit/package.json

Knowledge based on git-blame:
emmenko: 24%

visual-testing-app/package.json

Knowledge based on git-blame:
emmenko: 18%

yarn.lock

Knowledge based on git-blame:
emmenko: 52%

To learn more about /:\ gitStream - Visit our Docs

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
missing-jira 🤖 Type: Dependencies Dependency updates or something similar
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

0 participants