-
Notifications
You must be signed in to change notification settings - Fork 1
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
fix(deps): update react monorepo to v19 (major) #35
Open
renovate
wants to merge
1
commit into
main
Choose a base branch
from
renovate/major-react-monorepo
base: main
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
renovate
bot
force-pushed
the
renovate/major-react-monorepo
branch
4 times, most recently
from
April 28, 2022 04:53
c315b68
to
33aa10d
Compare
renovate
bot
force-pushed
the
renovate/major-react-monorepo
branch
2 times, most recently
from
May 17, 2022 10:22
d06eedd
to
4bb2d6b
Compare
renovate
bot
force-pushed
the
renovate/major-react-monorepo
branch
2 times, most recently
from
May 23, 2022 05:06
66117cf
to
ff4f129
Compare
renovate
bot
force-pushed
the
renovate/major-react-monorepo
branch
2 times, most recently
from
June 6, 2022 03:37
926bdae
to
7113d47
Compare
renovate
bot
force-pushed
the
renovate/major-react-monorepo
branch
2 times, most recently
from
June 14, 2022 22:10
3a5f59d
to
02f9161
Compare
renovate
bot
force-pushed
the
renovate/major-react-monorepo
branch
from
July 4, 2022 03:04
02f9161
to
7077965
Compare
renovate
bot
force-pushed
the
renovate/major-react-monorepo
branch
2 times, most recently
from
August 11, 2022 05:12
6e99987
to
dbadf8d
Compare
renovate
bot
force-pushed
the
renovate/major-react-monorepo
branch
from
August 26, 2022 16:11
dbadf8d
to
e297601
Compare
renovate
bot
force-pushed
the
renovate/major-react-monorepo
branch
from
October 26, 2022 13:30
e297601
to
c5cd8d6
Compare
renovate
bot
force-pushed
the
renovate/major-react-monorepo
branch
2 times, most recently
from
March 16, 2023 11:53
d80cb10
to
dcee58b
Compare
renovate
bot
force-pushed
the
renovate/major-react-monorepo
branch
2 times, most recently
from
June 7, 2023 21:16
2d4fbc9
to
fbf351d
Compare
renovate
bot
force-pushed
the
renovate/major-react-monorepo
branch
3 times, most recently
from
June 12, 2023 19:14
45ffbf8
to
cb4b5d7
Compare
renovate
bot
force-pushed
the
renovate/major-react-monorepo
branch
2 times, most recently
from
June 23, 2023 22:03
679b376
to
8d2b5e4
Compare
renovate
bot
force-pushed
the
renovate/major-react-monorepo
branch
2 times, most recently
from
July 13, 2023 17:36
e16323b
to
967cbb1
Compare
renovate
bot
force-pushed
the
renovate/major-react-monorepo
branch
from
July 25, 2023 01:26
967cbb1
to
cdddc3e
Compare
renovate
bot
force-pushed
the
renovate/major-react-monorepo
branch
2 times, most recently
from
April 8, 2024 23:36
0c7d523
to
d9f2fa8
Compare
renovate
bot
force-pushed
the
renovate/major-react-monorepo
branch
4 times, most recently
from
April 16, 2024 00:47
28b44bd
to
f51ef85
Compare
renovate
bot
force-pushed
the
renovate/major-react-monorepo
branch
4 times, most recently
from
April 26, 2024 23:10
a29617a
to
61a06ea
Compare
renovate
bot
force-pushed
the
renovate/major-react-monorepo
branch
from
May 11, 2024 13:44
61a06ea
to
2afe46b
Compare
renovate
bot
force-pushed
the
renovate/major-react-monorepo
branch
from
May 23, 2024 21:36
2afe46b
to
15a04ba
Compare
renovate
bot
force-pushed
the
renovate/major-react-monorepo
branch
from
August 20, 2024 22:42
15a04ba
to
f5d5c81
Compare
renovate
bot
force-pushed
the
renovate/major-react-monorepo
branch
from
August 30, 2024 13:54
f5d5c81
to
a95a31b
Compare
renovate
bot
force-pushed
the
renovate/major-react-monorepo
branch
3 times, most recently
from
September 19, 2024 21:03
02cc1ca
to
23bebd7
Compare
renovate
bot
force-pushed
the
renovate/major-react-monorepo
branch
2 times, most recently
from
September 27, 2024 18:57
eca5f1f
to
eb435a8
Compare
renovate
bot
force-pushed
the
renovate/major-react-monorepo
branch
from
October 2, 2024 16:43
eb435a8
to
983c65c
Compare
renovate
bot
force-pushed
the
renovate/major-react-monorepo
branch
from
October 11, 2024 16:05
983c65c
to
a5dc49d
Compare
renovate
bot
force-pushed
the
renovate/major-react-monorepo
branch
from
October 23, 2024 06:19
a5dc49d
to
ce5c094
Compare
renovate
bot
force-pushed
the
renovate/major-react-monorepo
branch
2 times, most recently
from
December 5, 2024 20:35
f78ae30
to
6251b3b
Compare
renovate
bot
changed the title
fix(deps): update react monorepo to v18 (major)
fix(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 23:25
4ec7d99
to
4013149
Compare
renovate
bot
force-pushed
the
renovate/major-react-monorepo
branch
from
December 18, 2024 17:57
4013149
to
7c220d6
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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:
17.0.45
->19.0.2
17.0.17
->19.0.2
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.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.
This PR was generated by Mend Renovate. View the repository job log.