feat: add eslint-plugin-react@7.36.0

[minwe]

See jsx-eslint/eslint-plugin-react#3819

Summary by CodeRabbit

• Chores
  • Updated dependency management for eslint-plugin-react to ensure alignment with the latest stable releases.

[coderabbitai]

Walkthrough

The pull request introduces updates to the package.json file, specifically in the peerDependencies section. It adds a new entry for the eslint-plugin-react package, indicating a version dependency change from 7.35.2 to 7.36.0, with a reference to a related GitHub issue. This update aims to maintain current dependencies and address potential issues.

Changes

File	Change Summary
package.json	Added "7.36.0": { "version": "7.35.2", "reason": "https://github.com/jsx-eslint/eslint-plugin-react/issues/3819" } in peerDependencies.

Poem

In the garden of code, we hop and play,
With eslint-plugin-react, we update today.
A version so bright, it shines like the sun,
Keeping our project healthy, oh what fun!
With each little change, our dependencies dance,
A leap into stability, we take a chance! 🐇✨

---

Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL

Commits

Files that changed from the base of the PR and between 6a8cdcf and 8cbf5a4.

Files selected for processing (1)

• package.json (1 hunks)

Additional comments not posted (1)

package.json (1)

501-504: Verify compatibility and reasoning for introducing eslint-plugin-react@7.36.0.

I see that you're introducing a new version 7.36.0 of eslint-plugin-react and specifying its peer dependency on 7.35.2.

A few things to verify and consider:

• Have you tested this version upgrade to ensure it doesn't introduce any breaking changes or compatibility issues with other dependencies in our project?
• The linked GitHub issue [Bug]: "Do not use isMounted" linting errors after upgrading to latest eslint-plugin-react (v7.36.0) jsx-eslint/eslint-plugin-react#3819 likely provides context for this change. Could you summarize the key reasons or benefits that motivated introducing this new version? Knowing the rationale can help reviewers better understand the change.

---

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.
  • @coderabbitai help me debug CodeRabbit configuration file.

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 using PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration 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.