fix(deps): update react monorepo to v18.3.1
This PR contains the following updates:
| Package | Change | Age | Confidence |
|---|---|---|---|
| react (source) | 18.1.0 -> 18.3.1 |
||
| react-test-renderer (source) | 18.1.0 -> 18.3.1 |
Release Notes
facebook/react (react)
v18.3.1
- Export
actfromreactf1338f
v18.3.0
This release is identical to 18.2 but adds warnings for deprecated APIs and other changes that are needed for React 19.
Read the React 19 Upgrade Guide for more info.
React
- Allow writing to
this.refsto support string ref codemod 909071 - Warn for deprecated
findDOMNodeoutside StrictMode c3b283 - Warn for deprecated
test-utilsmethods d4ea75 - Warn for deprecated Legacy Context outside StrictMode 415ee0
- Warn for deprecated string refs outside StrictMode #25383
- Warn for deprecated
defaultPropsfor function components #25699 - Warn when spreading
key#25697 - Warn when using
actfromtest-utilsd4ea75
React DOM
- Warn for deprecated
unmountComponentAtNode8a015b - Warn for deprecated
renderToStaticNodeStream#28874
v18.2.0
React DOM
- Provide a component stack as a second argument to
onRecoverableError. (@gnoff in #24591) - Fix hydrating into
documentcausing a blank page on mismatch. (@gnoff in #24523) - Fix false positive hydration errors with Suspense. (@gnoff in #24480 and @acdlite in #24532)
- Fix ignored
setStatein Safari when adding an iframe. (@gaearon in #24459)
React DOM Server
- Pass information about server errors to the client. (@salazarm and @gnoff in #24551 and #24591)
- Allow to provide a reason when aborting the HTML stream. (@gnoff in #24680)
- Eliminate extraneous text separators in the HTML where possible. (@gnoff in #24630)
- Disallow complex children inside
<title>elements to match the browser constraints. (@gnoff in #24679) - Fix buffering in some worker environments by explicitly setting
highWaterMarkto0. (@jplhomer in #24641)
Server Components (Experimental)
Configuration
📅 Schedule: Branch creation - "after 6pm every weekday,before 5am every weekday,every weekend" in timezone Europe/Berlin, Automerge - At any time (no schedule defined).
🚦 Automerge: Enabled.
♻ 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.
- [ ] If you want to rebase/retry this PR, check this box
This PR was generated by Mend Renovate. View the repository job log.
⚠ 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: compass-numapp-template/package-lock.json
npm error code ERESOLVE
npm error ERESOLVE could not resolve
npm error
npm error While resolving: [email protected]
npm error Found: [email protected]
npm error node_modules/react
npm error react@"18.3.1" from the root project
npm error peer react@"*" from @react-native-firebase/[email protected]
npm error node_modules/@react-native-firebase/app
npm error @react-native-firebase/app@"18.3.0" from the root project
npm error peer @react-native-firebase/app@"18.3.0" from @react-native-firebase/[email protected]
npm error node_modules/@react-native-firebase/messaging
npm error @react-native-firebase/messaging@"18.3.0" from the root project
npm error 23 more (@react-native-picker/picker, @react-navigation/core, ...)
npm error
npm error Could not resolve dependency:
npm error peer react@"18.1.0" from [email protected]
npm error node_modules/react-native
npm error react-native@"0.70.6" from the root project
npm error peer react-native@"*" from @react-native-firebase/[email protected]
npm error node_modules/@react-native-firebase/app
npm error @react-native-firebase/app@"18.3.0" from the root project
npm error 1 more (@react-native-firebase/messaging)
npm error 20 more (@react-native-picker/picker, ...)
npm error
npm error Conflicting peer dependency: [email protected]
npm error node_modules/react
npm error peer react@"18.1.0" from [email protected]
npm error node_modules/react-native
npm error react-native@"0.70.6" from the root project
npm error peer react-native@"*" from @react-native-firebase/[email protected]
npm error node_modules/@react-native-firebase/app
npm error @react-native-firebase/app@"18.3.0" from the root project
npm error 1 more (@react-native-firebase/messaging)
npm error 20 more (@react-native-picker/picker, ...)
npm error
npm error Fix the upstream dependency conflict, or retry
npm error this command with --force or --legacy-peer-deps
npm error to accept an incorrect (and potentially broken) dependency resolution.
npm error
npm error
npm error For a full report see:
npm error /tmp/renovate/cache/others/npm/_logs/2024-04-26T19_46_13_055Z-eresolve-report.txt
npm error A complete log of this run can be found in: /tmp/renovate/cache/others/npm/_logs/2024-04-26T19_46_13_055Z-debug-0.log
⚠️ 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: compass-numapp-template/package-lock.json
npm error code ERESOLVE
npm error ERESOLVE could not resolve
npm error
npm error While resolving: [email protected]
npm error Found: [email protected]
npm error node_modules/react
npm error react@"18.3.1" from the root project
npm error peer react@"*" from @react-native-firebase/[email protected]
npm error node_modules/@react-native-firebase/app
npm error @react-native-firebase/app@"18.3.0" from the root project
npm error peer @react-native-firebase/app@"18.3.0" from @react-native-firebase/[email protected]
npm error node_modules/@react-native-firebase/messaging
npm error @react-native-firebase/messaging@"18.3.0" from the root project
npm error 24 more (@react-native-picker/picker, @react-navigation/core, ...)
npm error
npm error Could not resolve dependency:
npm error peer react@"18.1.0" from [email protected]
npm error node_modules/react-native
npm error react-native@"0.70.6" from the root project
npm error peer react-native@"*" from @react-native-firebase/[email protected]
npm error node_modules/@react-native-firebase/app
npm error @react-native-firebase/app@"18.3.0" from the root project
npm error 1 more (@react-native-firebase/messaging)
npm error 20 more (@react-native-picker/picker, ...)
npm error
npm error Conflicting peer dependency: [email protected]
npm error node_modules/react
npm error peer react@"18.1.0" from [email protected]
npm error node_modules/react-native
npm error react-native@"0.70.6" from the root project
npm error peer react-native@"*" from @react-native-firebase/[email protected]
npm error node_modules/@react-native-firebase/app
npm error @react-native-firebase/app@"18.3.0" from the root project
npm error 1 more (@react-native-firebase/messaging)
npm error 20 more (@react-native-picker/picker, ...)
npm error
npm error Fix the upstream dependency conflict, or retry
npm error this command with --force or --legacy-peer-deps
npm error to accept an incorrect (and potentially broken) dependency resolution.
npm error
npm error
npm error For a full report see:
npm error /tmp/renovate/cache/others/npm/_logs/2024-12-02T14_09_52_767Z-eresolve-report.txt
npm error A complete log of this run can be found in: /tmp/renovate/cache/others/npm/_logs/2024-12-02T14_09_52_767Z-debug-0.log