-
Notifications
You must be signed in to change notification settings - Fork 12
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 v19 (major) #226
Open
renovate
wants to merge
1
commit into
master
Choose a base branch
from
renovate/major-react-monorepo
base: master
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
⚠ Artifact update problemRenovate 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:
The artifact failure details are included below: File name: package-lock.json
|
renovate
bot
force-pushed
the
renovate/major-react-monorepo
branch
2 times, most recently
from
November 28, 2022 12:01
4989c6d
to
3170a8b
Compare
renovate
bot
force-pushed
the
renovate/major-react-monorepo
branch
4 times, most recently
from
December 15, 2022 23:37
b4b519f
to
5607c18
Compare
renovate
bot
force-pushed
the
renovate/major-react-monorepo
branch
5 times, most recently
from
December 22, 2022 00:42
e38d4f1
to
2cf65b1
Compare
renovate
bot
force-pushed
the
renovate/major-react-monorepo
branch
from
December 25, 2022 21:09
2cf65b1
to
ac70bef
Compare
renovate
bot
force-pushed
the
renovate/major-react-monorepo
branch
3 times, most recently
from
January 15, 2023 22:16
3714a95
to
ac3e9d5
Compare
renovate
bot
force-pushed
the
renovate/major-react-monorepo
branch
5 times, most recently
from
January 25, 2023 14:27
f45970f
to
e300b3e
Compare
renovate
bot
force-pushed
the
renovate/major-react-monorepo
branch
6 times, most recently
from
February 6, 2023 08:50
cfade4e
to
77b9bce
Compare
renovate
bot
force-pushed
the
renovate/major-react-monorepo
branch
from
February 13, 2023 09:27
77b9bce
to
b9bb11a
Compare
renovate
bot
force-pushed
the
renovate/major-react-monorepo
branch
from
February 20, 2023 13:19
b9bb11a
to
77e706d
Compare
renovate
bot
force-pushed
the
renovate/major-react-monorepo
branch
from
March 3, 2023 13:18
77e706d
to
56098b3
Compare
renovate
bot
force-pushed
the
renovate/major-react-monorepo
branch
2 times, most recently
from
August 19, 2024 06:14
69e11b0
to
bcaddc7
Compare
renovate
bot
force-pushed
the
renovate/major-react-monorepo
branch
2 times, most recently
from
August 26, 2024 07:07
79c6869
to
4c266fe
Compare
renovate
bot
force-pushed
the
renovate/major-react-monorepo
branch
from
September 2, 2024 07:51
4c266fe
to
22b4284
Compare
renovate
bot
force-pushed
the
renovate/major-react-monorepo
branch
2 times, most recently
from
September 16, 2024 09:33
4bff815
to
bc8594c
Compare
renovate
bot
force-pushed
the
renovate/major-react-monorepo
branch
3 times, most recently
from
September 23, 2024 11:23
c647b10
to
133f160
Compare
renovate
bot
force-pushed
the
renovate/major-react-monorepo
branch
3 times, most recently
from
October 2, 2024 08:17
10a2192
to
6acec13
Compare
renovate
bot
force-pushed
the
renovate/major-react-monorepo
branch
2 times, most recently
from
October 14, 2024 06:30
63c4a80
to
f45330e
Compare
renovate
bot
force-pushed
the
renovate/major-react-monorepo
branch
from
October 21, 2024 06:27
f45330e
to
5fcd270
Compare
renovate
bot
force-pushed
the
renovate/major-react-monorepo
branch
2 times, most recently
from
November 11, 2024 11:19
01b45a5
to
b369633
Compare
renovate
bot
force-pushed
the
renovate/major-react-monorepo
branch
2 times, most recently
from
November 25, 2024 10:32
b985648
to
741ef0c
Compare
renovate
bot
force-pushed
the
renovate/major-react-monorepo
branch
2 times, most recently
from
December 2, 2024 08:56
b549f53
to
8f61ac4
Compare
renovate
bot
force-pushed
the
renovate/major-react-monorepo
branch
from
December 5, 2024 18:54
8f61ac4
to
760a029
Compare
renovate
bot
changed the title
chore(deps): update react monorepo to v18 (major)
chore(deps): update react monorepo to v19 (major)
Dec 5, 2024
renovate
bot
force-pushed
the
renovate/major-react-monorepo
branch
3 times, most recently
from
December 9, 2024 16:55
5c6b1e7
to
dd5d4fd
Compare
renovate
bot
force-pushed
the
renovate/major-react-monorepo
branch
from
December 16, 2024 09:46
dd5d4fd
to
3222195
Compare
renovate
bot
force-pushed
the
renovate/major-react-monorepo
branch
from
December 16, 2024 12:41
3222195
to
6c43801
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
None yet
0 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
^16.9.0 || ^17.0.0
->^16.9.0 || ^17.0.0 || ^19.0.0
17.0.2
->19.0.0
^16.9.0 || ^17.0.0
->^16.9.0 || ^17.0.0 || ^19.0.0
17.0.2
->19.0.0
17.0.2
->19.0.0
Release Notes
facebook/react (react)
v19.0.0
Compare Source
v18.3.1
Compare Source
v18.3.0
Compare Source
v18.2.0
Compare Source
React DOM
onRecoverableError
. (@gnoff in #24591)document
causing a blank page on mismatch. (@gnoff in #24523)setState
in Safari when adding an iframe. (@gaearon in #24459)React DOM Server
<title>
elements to match the browser constraints. (@gnoff in #24679)highWaterMark
to0
. (@jplhomer in #24641)Server Components (Experimental)
useId()
inside Server Components. (@gnoff in #24172)v18.1.0
Compare Source
React DOM
react-dom/client
when using UMD bundle. (@alireza-molaee in #24274)suppressHydrationWarning
to work in production too. (@gaearon in #24271)componentWillUnmount
firing twice inside of Suspense. (@acdlite in #24308)useDeferredValue
causing an infinite loop when passed an unmemoized value. (@acdlite in #24247)setState
loop inuseEffect
. (@gaearon in #24298)setState
inuseInsertionEffect
. (@gaearon in #24295)React DOM Server
bootstrapScriptContent
contents. (@gnoff in #24385)renderToPipeableStream
. (@gnoff in #24291)ESLint Plugin: React Hooks
Use Subscription
use-sync-external-store
shim. (@gaearon in #24289)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
anduseTransition
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 foruseEffect
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 torender
orunmount
. Use it instead ofReactDOM.render
. New features in React 18 don't work without it.hydrateRoot
: New method to hydrate a server rendered application. Use it instead ofReactDOM.hydrate
in conjunction with the new React DOM Server APIs. New features in React 18 don't work without it.Both
createRoot
andhydrateRoot
accept a new option calledonRecoverableError
in case you want to be notified when React recovers from errors during rendering or hydration for logging. By default, React will usereportError
, orconsole.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)
v19.0.0
Compare Source
v18.3.1
Compare Source
v18.3.0
Compare Source
v18.2.0
Compare Source
React DOM
onRecoverableError
. (@gnoff in #24591)document
causing a blank page on mismatch. (@gnoff in #24523)setState
in Safari when adding an iframe. (@gaearon in #24459)React DOM Server
<title>
elements to match the browser constraints. (@gnoff in #24679)highWaterMark
to0
. (@jplhomer in #24641)Server Components (Experimental)
useId()
inside Server Components. (@gnoff in #24172)v18.1.0
Compare Source
React DOM
react-dom/client
when using UMD bundle. (@alireza-molaee in #24274)suppressHydrationWarning
to work in production too. (@gaearon in #24271)componentWillUnmount
firing twice inside of Suspense. (@acdlite in #24308)useDeferredValue
causing an infinite loop when passed an unmemoized value. (@acdlite in #24247)setState
loop inuseEffect
. (@gaearon in #24298)setState
inuseInsertionEffect
. (@gaearon in #24295)React DOM Server
bootstrapScriptContent
contents. (@gnoff in #24385)renderToPipeableStream
. (@gnoff in #24291)ESLint Plugin: React Hooks
Use Subscription
use-sync-external-store
shim. (@gaearon in #24289)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
anduseTransition
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 foruseEffect
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 torender
orunmount
. Use it instead ofReactDOM.render
. New features in React 18 don't work without it.hydrateRoot
: New method to hydrate a server rendered application. Use it instead ofReactDOM.hydrate
in conjunction with the new React DOM Server APIs. New features in React 18 don't work without it.Both
createRoot
andhydrateRoot
accept a new option calledonRecoverableError
in case you want to be notified when React recovers from errors during rendering or hydration for logging. By default, React will usereportError
, orconsole.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)
v19.0.0
Compare Source
v18.3.1
Compare Source
v18.3.0
Compare Source
v18.2.0
Compare Source
React DOM
onRecoverableError
. (@gnoff in #24591)document
causing a blank page on mismatch. (@gnoff in #24523)setState
in Safari when adding an iframe. (@gaearon in #24459)React DOM Server
<title>
elements to match the browser constraints. (@gnoff in #24679)highWaterMark
to0
. (@jplhomer in #24641)Server Components (Experimental)
useId()
inside Server Components. (@gnoff in #24172)v18.1.0
Compare Source
React DOM
react-dom/client
when using UMD bundle. (@alireza-molaee in #24274)suppressHydrationWarning
to work in production too. (@gaearon in #24271)componentWillUnmount
firing twice inside of Suspense. (@acdlite in #24308)useDeferredValue
causing an infinite loop when passed an unmemoized value. (@acdlite in #24247)setState
loop inuseEffect
. (@gaearon in #24298)setState
inuseInsertionEffect
. (@gaearon in #24295)React DOM Server
bootstrapScriptContent
contents. (@gnoff in #24385)renderToPipeableStream
. (@gnoff in #24291)ESLint Plugin: React Hooks
Use Subscription
use-sync-external-store
shim. (@gaearon in #24289)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
anduseTransition
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 foruseEffect
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 torender
orunmount
. Use it instead ofReactDOM.render
. New features in React 18 don't work without it.hydrateRoot
: New method to hydrate a server rendered application. Use it instead ofReactDOM.hydrate
in conjunction with the new React DOM Server APIs. New features in React 18 don't work without it.Both
createRoot
andhydrateRoot
accept a new option calledonRecoverableError
in case you want to be notified when React recovers from errors during rendering or hydration for logging. By default, React will usereportError
, orconsole.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 - "* 0-3 * * 1" 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.
This PR was generated by Mend Renovate. View the repository job log.