-
-
Notifications
You must be signed in to change notification settings - Fork 74
chore: update react monorepo #809
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
base: main
Are you sure you want to change the base?
Conversation
✅ Deploy Preview for new-eslint ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
✅ Deploy Preview for hi-eslint ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
✅ Deploy Preview for ja-eslint ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
✅ Deploy Preview for es-eslint ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
✅ Deploy Preview for pt-br-eslint ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
✅ Deploy Preview for de-eslint ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
✅ Deploy Preview for zh-hans-eslint ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
✅ Deploy Preview for fr-eslint ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
4313109
to
f3b7ffe
Compare
This PR contains the following updates:
6.0.0-rc1
->6.1.1
19.1.1
->19.2.0
19.1.1
->19.2.0
Release Notes
facebook/react (eslint-plugin-react-hooks)
v6.1.1
Compare Source
Note: 6.1.0 accidentally allowed use of
recommended
without flat config, causing errors when used with ESLint v9'sdefineConfig()
helper. This has been fixed in 6.1.1.recommended
config for flat config compatibility. Therecommended
config has been converted to flat config format. Non-flat config users should userecommended-legacy
instead. (@poteto in #34700)recommended-latest
andrecommended-latest-legacy
configs that include React Compiler rules. (@poteto in #34675)NoUnusedOptOutDirectives
rule. (@poteto in #34703)hermes-parser
and dependency. (@poteto in #34719)@babel/plugin-proposal-private-methods
dependency. (@ArnaudBarre and @josephsavona in #34715)v6.1.0
Compare Source
Note: Version 6.0.0 was mistakenly released and immediately deprecated and untagged on npm. This is the first official 6.x major release and includes breaking changes.
recommended
preset. Legacy config moved torecommended-legacy
. (@michaelfaith in #32457)use
within try/catch blocks. (@poteto in #34040)useEffectEvent
functions in arbitrary closures. (@jbrown215 in #33544)React.useEffect
in addition touseEffect
in rules-of-hooks. (@Ayc0 in #34076)react-hooks
settings config option that to acceptadditionalEffectHooks
that are used across exhaustive-deps and rules-of-hooks rules. (@jbrown215) in #34497v6.0.0
Compare Source
Accidentally released. See 6.1.0 for the actual changes.
facebook/react (react)
v19.2.0
Compare Source
Below is a list of all new features, APIs, and bug fixes.
Read the React 19.2 release post for more information.
New React Features
<Activity>
: A new API to hide and restore the UI and internal state of its children.useEffectEvent
is a React Hook that lets you extract non-reactive logic into an Effect Event.cacheSignal
(for RSCs) lets your know when thecache()
lifetime is over.New React DOM Features
resume
: to resume a prerender to a stream.resumeAndPrerender
: to resume a prerender to HTML.resumeToPipeableStream
: to resume a prerender to a stream.resumeAndPrerenderToNodeStream
: to resume a prerender to HTML.prerender
APIs to return apostponed
state that can be passed to theresume
APIs.Notable changes
<ViewTransition>
Component. React will batch as much reveals as possible before the first paint while trying to hit popular first-contentful paint metrics.prerender
,renderToReadableStream
) to server-side-rendering APIs for Node.js:
IDs generated by useIdAll Changes
React
<Activity />
was developed over many years, starting beforeClassComponent.setState
(@acdlite @sebmarkbage and many others)%o
placeholder (@eps1lon #34198)useDeferredValue
loop in popstate event (@acdlite #32821)useDeferredValue
(@acdlite #34376)cacheSignal
(@sebmarkbage #33557)React DOM
:
for IDs generated byuseId
(@sebmarkbage, @eps1lon: #32001, #33342#33099, #33422)nonce
to be used on hoistable styles (@Andarist #32461)React.use
insideReact.lazy
-ed Component (@hi-ogawa #33941)progressiveChunkSize
option for server-side-rendering APIs (@sebmarkbage #33027)React Server Components
<img>
and<link>
using hints before they're rendered (@sebmarkbage #34604)filterStackFrame
(@eps1lon #33707)React Reconciler
on*
handlers to account for upcoming experimental APIsConfiguration
📅 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.
👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.
This PR was generated by Mend Renovate. View the repository job log.