chore(deps): update react monorepo

[playerdata-bot]

This PR contains the following updates:

Package	Type	Update	Change
@types/react (source)	devDependencies	minor	18.2.79 -> 18.3.8
react (source)	dependencies	minor	18.2.0 -> 18.3.1

---

Release Notes

facebook/react (react)

v18.3.1

Compare Source

• Export act from react f1338f

v18.3.0

Compare Source

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.refs to support string ref codemod 909071
• Warn for deprecated findDOMNode outside StrictMode c3b283
• Warn for deprecated test-utils methods d4ea75
• Warn for deprecated Legacy Context outside StrictMode 415ee0
• Warn for deprecated string refs outside StrictMode #​25383
• Warn for deprecated defaultProps for function components #​25699
• Warn when spreading key #​25697
• Warn when using act from test-utils d4ea75

React DOM

• Warn for deprecated unmountComponentAtNode 8a015b
• Warn for deprecated renderToStaticNodeStream #​28874

---

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Enabled.

♻ 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.

---

• If you want to rebase/retry this PR, check this box

---

This PR has been generated by Renovate Bot.

[playerdata-bot]

⚠ Artifact update problem

Renovate failed to update artifacts 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: 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@">=16.9.0" from @testing-library/[email protected]
npm error   node_modules/@testing-library/react-hooks
npm error     @testing-library/react-hooks@"^7.0.1" from [email protected]
npm error     node_modules/expo-module-scripts
npm error       dev expo-module-scripts@"^3.4.0" from the root project
npm error   3 more (react-error-boundary, react-shallow-renderer, react-test-renderer)
npm error
npm error Could not resolve dependency:
npm error peer react@"18.2.0" from [email protected]
npm error node_modules/react-native
npm error   peer react-native@"*" from the root project
npm error   peer react-native@"*" from @react-native/[email protected]
npm error   node_modules/@react-native/virtualized-lists
npm error     @react-native/virtualized-lists@"0.73.4" from [email protected]
npm error
npm error Conflicting peer dependency: [email protected]
npm error node_modules/react
npm error   peer react@"18.2.0" from [email protected]
npm error   node_modules/react-native
npm error     peer react-native@"*" from the root project
npm error     peer react-native@"*" from @react-native/[email protected]
npm error     node_modules/@react-native/virtualized-lists
npm error       @react-native/virtualized-lists@"0.73.4" from [email protected]
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-07-04T09_16_33_067Z-eresolve-report.txt
npm error A complete log of this run can be found in: /tmp/renovate/cache/others/npm/_logs/2024-07-04T09_16_33_067Z-debug-0.log

File name: example/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 [email protected]
npm error   node_modules/react-native-ble-plx
npm error     react-native-ble-plx@"3.2.0" from the root project
npm error   3 more (react-native-document-picker, ...)
npm error
npm error Could not resolve dependency:
npm error peer react@"18.2.0" from [email protected]
npm error node_modules/react-native
npm error   react-native@"0.73.6" from the root project
npm error   peer react-native@"*" from @react-native/[email protected]
npm error   node_modules/@react-native/virtualized-lists
npm error     @react-native/virtualized-lists@"0.73.4" from [email protected]
npm error   4 more (react-native-ble-plx, react-native-document-picker, ...)
npm error
npm error Conflicting peer dependency: [email protected]
npm error node_modules/react
npm error   peer react@"18.2.0" from [email protected]
npm error   node_modules/react-native
npm error     react-native@"0.73.6" from the root project
npm error     peer react-native@"*" from @react-native/[email protected]
npm error     node_modules/@react-native/virtualized-lists
npm error       @react-native/virtualized-lists@"0.73.4" from [email protected]
npm error     4 more (react-native-ble-plx, react-native-document-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-07-04T09_16_36_043Z-eresolve-report.txt
npm error A complete log of this run can be found in: /tmp/renovate/cache/others/npm/_logs/2024-07-04T09_16_36_043Z-debug-0.log

[saty9]

blocking behind #302 as needs a react native bump

[coderabbitai]

Warning

Rate Limit Exceeded

@playerdata-bot has exceeded the limit for the number of commits or files that can be reviewed per hour. Please wait 29 minutes and 25 seconds before requesting another review.

How to resolve this issue?

After the wait time has elapsed, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

We recommend that you space out your commits to avoid hitting the rate limit.

How do rate limits work?

CodeRabbit enforces hourly rate limits for each developer per organization.
Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout.
Please see our FAQ for further information.

Commits

Files that changed from the base of the PR and between 4b80416 and af0ef0a.

---

Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

Share

• X
• Mastodon
• Reddit
• LinkedIn

Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>.
  • Generate unit testing code for this file.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai generate unit testing code for this file.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai generate interesting stats about this repository and render them as a table.
  • @coderabbitai show all the console.log statements in this repository.
  • @coderabbitai read src/utils.ts and generate unit testing code.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (invoked as PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger a review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai help to get help.

Additionally, you can add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.

CodeRabbit Configration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.

[playerdata-bot]

⚠️ Artifact update problem

Renovate failed to update artifacts 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: 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@">=16.9.0" from @testing-library/[email protected]
npm error   node_modules/@testing-library/react-hooks
npm error     @testing-library/react-hooks@"^7.0.1" from [email protected]
npm error     node_modules/expo-module-scripts
npm error       dev expo-module-scripts@"^3.4.0" from the root project
npm error   3 more (react-error-boundary, react-shallow-renderer, react-test-renderer)
npm error
npm error Could not resolve dependency:
npm error peer react@"18.2.0" from [email protected]
npm error node_modules/react-native
npm error   peer react-native@"*" from the root project
npm error   peer react-native@"*" from @react-native/[email protected]
npm error   node_modules/@react-native/virtualized-lists
npm error     @react-native/virtualized-lists@"0.73.4" from [email protected]
npm error
npm error Conflicting peer dependency: [email protected]
npm error node_modules/react
npm error   peer react@"18.2.0" from [email protected]
npm error   node_modules/react-native
npm error     peer react-native@"*" from the root project
npm error     peer react-native@"*" from @react-native/[email protected]
npm error     node_modules/@react-native/virtualized-lists
npm error       @react-native/virtualized-lists@"0.73.4" from [email protected]
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-09-20T19_57_41_065Z-eresolve-report.txt
npm error A complete log of this run can be found in: /tmp/renovate/cache/others/npm/_logs/2024-09-20T19_57_41_065Z-debug-0.log

File name: example/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 [email protected]
npm error   node_modules/react-native-ble-plx
npm error     react-native-ble-plx@"3.2.1" from the root project
npm error   3 more (react-native-document-picker, ...)
npm error
npm error Could not resolve dependency:
npm error peer react@"18.2.0" from [email protected]
npm error node_modules/react-native
npm error   react-native@"0.73.6" from the root project
npm error   peer react-native@"*" from @react-native/[email protected]
npm error   node_modules/@react-native/virtualized-lists
npm error     @react-native/virtualized-lists@"0.73.4" from [email protected]
npm error   4 more (react-native-ble-plx, react-native-document-picker, ...)
npm error
npm error Conflicting peer dependency: [email protected]
npm error node_modules/react
npm error   peer react@"18.2.0" from [email protected]
npm error   node_modules/react-native
npm error     react-native@"0.73.6" from the root project
npm error     peer react-native@"*" from @react-native/[email protected]
npm error     node_modules/@react-native/virtualized-lists
npm error       @react-native/virtualized-lists@"0.73.4" from [email protected]
npm error     4 more (react-native-ble-plx, react-native-document-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-09-20T19_57_43_298Z-eresolve-report.txt
npm error A complete log of this run can be found in: /tmp/renovate/cache/others/npm/_logs/2024-09-20T19_57_43_298Z-debug-0.log