Skip to content
This repository has been archived by the owner on Oct 2, 2023. It is now read-only.

Update react monorepo to v18 (major) #24

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

Update react monorepo to v18 (major) #24

wants to merge 1 commit into from

Conversation

renovate[bot]
Copy link

@renovate renovate bot commented Aug 27, 2018 •
edited

Mend Renovate

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
react (source) 15.6.1 -> 18.2.0 age adoption passing confidence
react-dom (source) 15.6.1 -> 18.2.0 age adoption passing confidence

Release Notes

facebook/react (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)

v16.14.0

Compare Source

React

v16.13.1

Compare Source

React DOM
  • Fix bug in legacy mode Suspense where effect clean-up functions are not fired. This only affects users who use Suspense for data fetching in legacy mode, which is not technically supported. (@​acdlite in #​18238)
  • Revert warning for cross-component updates that happen inside class render lifecycles (componentWillReceiveProps, shouldComponentUpdate, and so on). (@​gaearon in #​18330)

v16.13.0

Compare Source

React
React DOM
Concurrent Mode (Experimental)

v16.12.0

Compare Source

React DOM
React Is

v16.11.0

Compare Source

React DOM
  • Fix mouseenter handlers from firing twice inside nested React containers. @​yuanoook in #​16928
  • Remove unstable_createRoot and unstable_createSyncRoot experimental APIs. (These are available in the Experimental channel as createRoot and createSyncRoot.) (@​acdlite in #​17088)

v16.10.2

Compare Source

React DOM
  • Fix regression in react-native-web by restoring order of arguments in event plugin extractors (@​necolas in #​16978)

v16.10.1

Compare Source

React DOM
  • Fix regression in Next.js apps by allowing Suspense mismatch during hydration to silently proceed (@​sebmarkbage in #​16943)

v16.10.0

Compare Source

React DOM
Scheduler (Experimental)
  • Improve queue performance by switching its internal data structure to a min binary heap. (@​acdlite in #​16245)
  • Use postMessage loop with short intervals instead of attempting to align to frame boundaries with requestAnimationFrame. (@​acdlite in #​16214)
useSubscription
  • Avoid tearing issue when a mutation happens and the previous update is still in progress. (@​bvaughn in #​16623)

v16.9.0

Compare Source

React
  • Add <React.Profiler> API for gathering performance measurements programmatically. (@​bvaughn in #​15172)
  • Remove unstable_ConcurrentMode in favor of unstable_createRoot. (@​acdlite in #​15532)
React DOM
React DOM Server
React Test Utilities and Test Renderer
ESLint Plugin: React Hooks

v16.8.6

Compare Source

React DOM

v16.8.5

Compare Source

React DOM
React DOM Server
React Shallow Renderer

v16.8.4

Compare Source

React DOM and other renderers
  • Fix a bug where DevTools caused a runtime error when inspecting a component that used a useContext hook. (@​bvaughn in #​14940)

v16.8.3

Compare Source

React DOM
React DOM Server
  • Unwind the context stack when a stream is destroyed without completing, to prevent incorrect values during a subsequent render. (@​overlookmotel in #​14706)
ESLint Plugin for React Hooks

v16.8.2

Compare Source

React DOM
React Test Utils and React Test Renderer

v16.8.1

Compare Source

React DOM and React Test Renderer
React Test Utils

v16.8.0

Compare Source

React
React DOM
React Test Renderer and Test Utils
  • Support Hooks in the shallow renderer. (@​trueadm in #​14567)
  • Fix wrong state in shouldComponentUpdate in the presence of getDerivedStateFromProps for Shallow Renderer. (@​chenesan in #​14613)
  • Add ReactTestRenderer.act() and ReactTestUtils.act() for batching updates so that tests more closely match real behavior. (@​threepointone in #​14744)
ESLint Plugin: React Hooks

v16.7.0

Compare Source

React DOM
Scheduler (Experimental)

v16.6.3

React DOM
React DOM Server

v16.6.2

This release was published in a broken state and should be skipped.

v16.6.1

Compare Source

React DOM
Scheduler (Experimental)

v16.6.0

Compare Source

React
React DOM
React DOM Server
Scheduler (Experimental)

v16.5.2

Compare Source

React DOM
Schedule (Experimental)

v16.5.1

Compare Source

React
React DOM
  • Fix a regression in unstable exports used by React Native Web. (@​aweary in #​13598)
  • Fix a crash when component defines a method called isReactComponent. (@​gaearon in #​13608)
  • Fix a crash in development mode in IE9 when printing a warning. (@​link-alex in #​13620)
  • Provide a better error message when running react-dom/profiling with schedule/tracking. (@​bvaughn in [#​13605

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.

@renovate renovate bot force-pushed the renovate/major-react-monorepo branch from 530a9d2 to 7f4155c Compare September 6, 2018 16:51
@renovate renovate bot force-pushed the renovate/major-react-monorepo branch 2 times, most recently from 616b704 to 7ea462b Compare September 18, 2018 19:43
@renovate renovate bot force-pushed the renovate/major-react-monorepo branch from 7ea462b to 6b34e67 Compare October 24, 2018 00:16
@renovate renovate bot force-pushed the renovate/major-react-monorepo branch 3 times, most recently from 7422cc1 to cfb6922 Compare November 13, 2018 04:01
@renovate renovate bot force-pushed the renovate/major-react-monorepo branch from cfb6922 to 3ca14ce Compare December 20, 2018 01:31
@renovate renovate bot force-pushed the renovate/major-react-monorepo branch 2 times, most recently from ba3f628 to f7d7d6b Compare February 6, 2019 18:33
@renovate renovate bot force-pushed the renovate/major-react-monorepo branch 2 times, most recently from 745d92f to 6ea510f Compare February 21, 2019 18:28
@renovate renovate bot force-pushed the renovate/major-react-monorepo branch from 6ea510f to f7e3878 Compare March 5, 2019 23:20
@renovate renovate bot force-pushed the renovate/major-react-monorepo branch 2 times, most recently from fcad112 to 7d2dec9 Compare March 28, 2019 09:44
@renovate renovate bot force-pushed the renovate/major-react-monorepo branch from 7d2dec9 to bbe2787 Compare August 10, 2019 13:58
@renovate renovate bot force-pushed the renovate/major-react-monorepo branch from bbe2787 to 81172a4 Compare October 5, 2019 09:49
@renovate renovate bot force-pushed the renovate/major-react-monorepo branch from 81172a4 to cc1926c Compare November 11, 2019 21:00
@renovate renovate bot force-pushed the renovate/major-react-monorepo branch from cc1926c to d24d91a Compare November 21, 2019 11:11
@renovate renovate bot force-pushed the renovate/major-react-monorepo branch from d24d91a to 82e4073 Compare March 14, 2020 22:01
@renovate renovate bot force-pushed the renovate/major-react-monorepo branch from 82e4073 to ed788a4 Compare April 26, 2020 21:02
@renovate renovate bot force-pushed the renovate/major-react-monorepo branch from ed788a4 to d4a9ea4 Compare October 29, 2020 11:02
@renovate renovate bot changed the title Update react monorepo to v16 (major) Update react monorepo to v17 (major) Oct 29, 2020
@renovate renovate bot force-pushed the renovate/major-react-monorepo branch from d4a9ea4 to db84ef3 Compare April 26, 2021 12:31
@renovate
Copy link
Author

renovate bot commented Apr 26, 2021

⚠️ 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 check 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: quarrelly-ui/package-lock.json
npm WARN old lockfile 
npm WARN old lockfile The package-lock.json file was created with an old version of npm,
npm WARN old lockfile so supplemental metadata must be fetched from the registry.
npm WARN old lockfile 
npm WARN old lockfile This is a one-time fix-up, please be patient...
npm WARN old lockfile 
npm ERR! code ERESOLVE
npm ERR! ERESOLVE unable to resolve dependency tree
npm ERR! 
npm ERR! Found: react@17.0.2
npm ERR! node_modules/react
npm ERR!   react@"17.0.2" from the root project
npm ERR!   peer react@"17.0.2" from react-dom@17.0.2
npm ERR!   node_modules/react-dom
npm ERR!     react-dom@"17.0.2" from the root project
npm ERR! 
npm ERR! Could not resolve dependency:
npm ERR! peer react@"0.14.x || 15.* || ^15.0.0 || ^16.0.0-alpha" from react-apollo@1.4.2
npm ERR! node_modules/react-apollo
npm ERR!   react-apollo@"1.4.2" 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/2021-04-26T12_30_47_476Z-debug.log

@renovate renovate bot force-pushed the renovate/major-react-monorepo branch from db84ef3 to 5245374 Compare April 24, 2022 18:12
@renovate renovate bot changed the title Update react monorepo to v17 (major) Update react monorepo to v18 (major) Apr 24, 2022
@renovate
Copy link
Author

renovate bot commented Apr 24, 2022 •
edited

⚠ 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: quarrelly-ui/package-lock.json

real	0m7.422s
user	0m6.418s
sys	0m0.772s
npm WARN old lockfile 
npm WARN old lockfile The package-lock.json file was created with an old version of npm,
npm WARN old lockfile so supplemental metadata must be fetched from the registry.
npm WARN old lockfile 
npm WARN old lockfile This is a one-time fix-up, please be patient...
npm WARN old lockfile 
npm WARN ERESOLVE overriding peer dependency
npm WARN While resolving: quarrelly-ui@0.1.0
npm WARN Found: react@15.6.1
npm WARN node_modules/react
npm WARN   react@"18.2.0" from the root project
npm WARN   5 more (react-apollo, react-dom, react-relay, ...)
npm WARN 
npm WARN Could not resolve dependency:
npm WARN peer react@"0.14.x || 15.* || ^15.0.0 || ^16.0.0-alpha" from react-apollo@1.4.2
npm WARN node_modules/react-apollo
npm WARN   react-apollo@"1.4.2" from the root project
npm WARN ERESOLVE overriding peer dependency
npm WARN While resolving: quarrelly-ui@0.1.0
npm WARN Found: react@15.6.1
npm WARN node_modules/react
npm WARN   react@"18.2.0" from the root project
npm WARN   5 more (react-apollo, react-dom, react-relay, ...)
npm WARN 
npm WARN Could not resolve dependency:
npm WARN peer react@"^15.6.1" from react-dom@15.6.1
npm WARN node_modules/react-dom
npm WARN   react-dom@"18.2.0" from the root project
npm WARN   2 more (react-apollo, react-virtualized)
npm WARN ERESOLVE overriding peer dependency
npm WARN While resolving: quarrelly-ui@0.1.0
npm WARN Found: react@15.6.1
npm WARN node_modules/react
npm WARN   react@"18.2.0" from the root project
npm WARN   5 more (react-apollo, react-dom, react-relay, ...)
npm WARN 
npm WARN Could not resolve dependency:
npm WARN peer react@"^16.0.0-a || ^15.0.0 || ^0.14.0" from react-relay@1.1.0
npm WARN node_modules/react-relay
npm WARN   react-relay@"1.1.0" from the root project
npm WARN ERESOLVE overriding peer dependency
npm WARN While resolving: quarrelly-ui@0.1.0
npm WARN Found: react@15.6.1
npm WARN node_modules/react
npm WARN   react@"18.2.0" from the root project
npm WARN   5 more (react-apollo, react-dom, react-relay, ...)
npm WARN 
npm WARN Could not resolve dependency:
npm WARN peer react@"^15.3.0 || ^16.0.0-alpha" from react-virtualized@9.8.0
npm WARN node_modules/react-virtualized
npm WARN   react-virtualized@"9.8.0" from the root project
npm WARN ERESOLVE overriding peer dependency
npm WARN ERESOLVE overriding peer dependency
npm ERR! code ERESOLVE
npm ERR! ERESOLVE could not resolve
npm ERR! 
npm ERR! While resolving: react-virtualized@9.8.0
npm ERR! Found: react-dom@18.2.0
npm ERR! node_modules/react-dom
npm ERR!   react-dom@"18.2.0" from the root project
npm ERR! 
npm ERR! Could not resolve dependency:
npm ERR! peer react-dom@"^15.3.0 || ^16.0.0-alpha" from react-virtualized@9.8.0
npm ERR! node_modules/react-virtualized
npm ERR!   react-virtualized@"9.8.0" from the root project
npm ERR! 
npm ERR! Conflicting peer dependency: react-dom@16.14.0
npm ERR! node_modules/react-dom
npm ERR!   peer react-dom@"^15.3.0 || ^16.0.0-alpha" from react-virtualized@9.8.0
npm ERR!   node_modules/react-virtualized
npm ERR!     react-virtualized@"9.8.0" 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/2022-06-18T16_57_57_353Z-debug-0.log

@renovate renovate bot force-pushed the renovate/major-react-monorepo branch from 5245374 to 1b89e4e Compare May 15, 2022 22:52
@renovate renovate bot force-pushed the renovate/major-react-monorepo branch from 1b89e4e to 1e678de Compare June 18, 2022 16:59
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
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.

None yet
0 participants