chore: remove unused dependencies

[divyeshagrawal]

Summary by CodeRabbit

• Chores
  • 优化了项目依赖配置，移除了不必要的开发依赖。此变更不影响应用功能。

[vercel]

@divyeshagrawal is attempting to deploy a commit to the React Component Team on Vercel.

A member of the Team first needs to authorize it.

[coderabbitai]

概览

从 package.json 的 devDependencies 中移除了 eslint-plugin-unicorn 依赖项。同时进行了轻微的尾部换行符格式调整，无功能影响。

变更

内聚体 / 文件	变更摘要
DevDependencies 清理 package.json	移除了 eslint-plugin-unicorn ^55.0.0 devDependency

预估审查工作量

🎯 1 (微不足道) | ⏱️ ~2 分钟

• 单一文件修改，仅涉及依赖项移除
• 无代码逻辑变化
• 无导出或公共 API 影响

诗歌

🐰 一根胡萝卜开始摘，
Unicorn 从此别离去，
依赖少一个没烦恼，
包更轻，心更爽！
✨

Pre-merge checks and finishing touches

❌ Failed checks (1 warning)

Check name	Status	Explanation	Resolution
Docstring Coverage	⚠️ Warning	Docstring coverage is 0.00% which is insufficient. The required threshold is 80.00%.	You can run @coderabbitai generate docstrings to improve docstring coverage.

✅ Passed checks (2 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title Check	✅ Passed	Pull request标题"chore: remove unused dependencies"与changeset的主要改变完全相关。标题清晰地描述了本次改动的核心内容——移除未使用的依赖项，这与实际改动（从package.json中移除eslint-plugin-unicorn devDependency）一致。标题简洁明了，避免了模糊措辞，能够让团队成员快速理解改动的目的。

✨ Finishing touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment

---

📜 Recent review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 2b96da4 and e3f7180.

📒 Files selected for processing (1)

• package.json (1 hunks)

🔇 Additional comments (1)

package.json (1)

48-67: 需要进行进一步验证，检查是否存在内联的 ESLint 配置。

需要检查 package.json 中是否存在内联的 ESLint 配置。

移除 eslint-plugin-unicorn 依赖是安全的

验证确认该依赖未在项目中使用：

• eslint-plugin-unicorn 是一个 ESLint 插件，需要在配置文件中显式引用（plugins 字段中）
• 搜索结果显示代码库中不存在任何 ESLint 配置文件（.eslintrc 或 eslint.config.js）
• 代码库中零次引用"unicorn"
• Lint 脚本正常工作，未依赖此插件

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[gemini-code-assist]

Summary of Changes

Hello @divyeshagrawal, I'm Gemini Code Assist¹! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request focuses on project maintenance by cleaning up the package.json file. It removes an unused development dependency, eslint-plugin-unicorn, which helps streamline the project's build process and reduce its footprint. Additionally, it addresses a minor formatting inconsistency by ensuring the package.json file ends with a newline character.

Highlights

• Dependency Removal: The development dependency eslint-plugin-unicorn has been removed from the package.json file.
• File Formatting: A missing newline character has been added to the end of the package.json file.

Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature	Command	Description
Code Review	/gemini review	Performs a code review for the current pull request in its current state.
Pull Request Summary	/gemini summary	Provides a summary of the current pull request in its current state.
Comment	@gemini-code-assist	Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help	/gemini help	Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution. ↩

[gemini-code-assist]

Code Review

This pull request removes the eslint-plugin-unicorn dependency, which is a straightforward change. However, it appears the trailing newline character has been removed from package.json. It is a widely-accepted best practice to end files with a newline for better compatibility with various development tools. I have added a suggestion to restore it.

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 100.00%. Comparing base (2b96da4) to head (e3f7180).
⚠️ Report is 1 commits behind head on master.

Additional details and impacted files

@@            Coverage Diff            @@
##            master      #508   +/-   ##
=========================================
  Coverage   100.00%   100.00%           
=========================================
  Files            3         3           
  Lines           37        37           
  Branches        15        15           
=========================================
  Hits            37        37           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.