Chore: Remove unused dependencies

[divyeshagrawal]

Summary by CodeRabbit

清理

• 清理
  • 精简项目依赖配置，移除了两个不再需要的开发依赖项

[coderabbitai]

步骤说明

从 package.json 文件中移除了两个开发依赖项：coveralls 和 cross-env。此更改简化了项目的依赖配置，不涉及其他脚本、依赖项或配置的修改。

变更内容

文件组 / 文件	变更总结
开发依赖移除 package.json	从 devDependencies 中移除 coveralls 和 cross-env 两个开发依赖

代码审核工作量评估

🎯 1 (平凡) | ⏱️ ~3 分钟

• 变更范围极小，仅涉及单一文件
• 无逻辑改动，纯粹的依赖清理
• 变更性质简单明确，无需深入分析

诗歌

🐰 依赖在减少，项目更轻盈，
不需的工具已离去，
代码库蹦蹦跳，清爽又欢喜！
✨ 过期的包裹扔掉了~

Pre-merge checks and finishing touches

✅ Passed checks (2 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	标题清晰准确地总结了主要改动：移除两个未使用的开发依赖项(coveralls 和 cross-env)。

✨ 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 f71d572 and 2d2f55d.

📒 Files selected for processing (1)

• package.json (0 hunks)

💤 Files with no reviewable changes (1)

• package.json

---

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 two development dependencies that are no longer in use, contributing to a leaner and more efficient project setup.

Highlights

• Dependency Removal: The development dependencies coveralls and cross-env have been removed from the package.json file, indicating they are no longer required for the project.

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 coveralls and cross-env dependencies. The removal of coveralls appears correct as your CI pipeline uses the coverallsapp/github-action, which doesn't require the coveralls npm package. However, I've identified a potential issue with removing cross-env, as it could negatively impact the development experience for Windows users. Please see the specific comment for details.

[gemini-code-assist]

Removing cross-env could introduce cross-platform compatibility issues. The gh-pages script in your package.json uses GH_PAGES=1 ..., which is a Unix-specific syntax for setting environment variables and will fail on Windows. To maintain support for developers on all platforms, it would be best to use cross-env in that script. For example: "gh-pages": "cross-env GH_PAGES=1 npm run docs:build && npm run docs:deploy". Please consider re-adding this dependency and updating the script.

[socket-security]

Review the following changes in direct dependencies. Learn more about Socket for GitHub.

Diff	Package	Supply Chain Security	Vulnerability	Quality	Maintenance	License
	husky@​9.1.7
	rc-test@​7.1.2
	less@​4.1.3 ⏵ 4.4.2	+1		+1
	father@​4.6.7
	gh-pages@​6.3.0
	dumi@​2.4.21
	react@​19.2.0
	pretty-quick@​4.2.2
	prettier@​3.6.2
	typescript@​5.9.3
	react-dom@​18.3.1 ⏵ 19.2.0	+1		+1
	lint-staged@​16.2.6
	eslint@​8.57.1

View full report

[codecov]

Codecov Report

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

Additional details and impacted files

@@           Coverage Diff           @@
##           master     #146   +/-   ##
=======================================
  Coverage   97.70%   97.70%           
=======================================
  Files           4        4           
  Lines         218      218           
  Branches       84       84           
=======================================
  Hits          213      213           
  Misses          5        5           

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