perf: uninstall classnames, install clsx

[li-jia-nan]

Summary by CodeRabbit

• 重构
  • 使用更轻量的类名组装工具替换原实现，优化样式类名拼接；对功能、对外 API 与界面表现无影响，交互保持一致。
• 杂务
  • 依赖调整：新增 clsx、@types/node、@rc-component/father-plugin；移除 classnames、@types/classnames；清理无用开发依赖，不影响安装与运行。
  • 更新忽略规则，排除 pnpm-lock.yaml，优化版本库清洁度。

[coderabbitai]

Note

Other AI code review bot(s) detected

CodeRabbit has detected other AI code review bot(s) in this pull request and will avoid duplicating their findings in the review comments. This may lead to a less comprehensive review.

Walkthrough

本次变更在仓库中新增忽略 pnpm-lock.yaml；在 package.json 中以 clsx 替换 classnames 并调整若干 devDependencies；在 src/Dropdown.tsx 中将 classnames 替换为 clsx，用于拼接 className，无导出或对外 API 改动。

Changes

Cohort / File(s)	Change Summary
Ignore Rules \.gitignore	新增忽略项：pnpm-lock.yaml。
Dependency Manifest package.json	移除 classnames，新增 clsx；移除 @types/classnames；新增 @rc-component/father-plugin 与 @types/node；临时加入后又移除 @rc-component/menu（最终不保留）。
Component Class Utility Migration src/Dropdown.tsx	将 classnames 替换为 clsx；更新相应 import 与调用处（元素 className 与 Trigger 的 popupClassName）；无对外 API 变化。

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~10 minutes

Suggested reviewers

• zombieJ

Poem

我用耳朵拂过键与键，咔嗒如春雨
classnames 跳下枝头，clsx 轻巧接续
锁文件被风轻掩，.gitignore 悄然记取
依赖排排站，我在草间点名不误
嘭——一只兔子提交了干净的版图 🐇✨

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	此标题以“perf:”前缀开头，简洁明确地表明了核心更改：将 classnames 卸载并安装 clsx，与提交中更新依赖项和代码导入的实际内容高度一致。

✨ Finishing touches

• 📝 Generate Docstrings

🧪 Generate unit tests

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch clsx-update

---

📜 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 6dafd0f and 2f7b5e0.

⛔ Files ignored due to path filters (1)

• tests/__snapshots__/basic.test.tsx.snap is excluded by !**/*.snap

📒 Files selected for processing (3)

• .gitignore (1 hunks)
• package.json (1 hunks)
• src/Dropdown.tsx (3 hunks)

🔇 Additional comments (1)

package.json (1)

47-60: 已确认移除 classnames 引用
仓库中不再存在 classnames 导入，依赖已切换至 clsx。

---

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 @li-jia-nan, 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 introduces a performance optimization by migrating the project's class name concatenation utility from classnames to clsx. This change is expected to yield a slightly smaller bundle size and potentially faster runtime execution when dynamically generating CSS classes. The update involves modifying the package.json dependencies and refactoring the relevant code in src/Dropdown.tsx to utilize the new utility. Additionally, the .gitignore file has been updated to include pnpm-lock.yaml.

Highlights

• Dependency Swap: Replaced the classnames utility library with clsx in the project dependencies. This change is primarily aimed at improving performance and reducing bundle size, as clsx is known for being a faster and lighter alternative.
• Code Refactor: Updated all instances of classNames function calls to clsx within src/Dropdown.tsx to align with the new dependency.
• Build Configuration Update: Added pnpm-lock.yaml to the .gitignore file, indicating potential support or usage of pnpm as a package manager.

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

[socket-security]

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

Diff	Package	Supply Chain Security	Vulnerability	Quality	Maintenance	License
	clsx@​2.1.1

View full report

[socket-security]

Warning

Review the following alerts detected in dependencies.

According to your organization's Security Policy, it is recommended to resolve "Warn" alerts. Learn more about Socket for GitHub.

Action	Severity	Alert  (click "▶" to expand/collapse)
Warn		safer-buffer@2.1.2 has Obfuscated code. Confidence: 0.94 Location: Package overview From: ? → npm/@rc-component/np@1.0.4 → npm/safer-buffer@2.1.2 ℹ Read more on: This package | This alert | What is obfuscated code? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev. Suggestion: Packages should not obfuscate their code. Consider not using packages with obfuscated code. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/safer-buffer@2.1.2. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.

View full report

[gemini-code-assist]

Code Review

This pull request replaces the classnames library with clsx for performance improvements, which is a good optimization. The changes are straightforward, involving updating package.json and the import/usage in Dropdown.tsx. I've found one critical issue with an invalid package version in package.json that will break dependency installation. I've also left a medium-severity suggestion to improve code consistency regarding the clsx import.

[codecov]

Codecov Report

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

Additional details and impacted files

@@           Coverage Diff           @@
##           master     #243   +/-   ##
=======================================
  Coverage   99.09%   99.09%           
=======================================
  Files           5        5           
  Lines         110      110           
  Branches       34       34           
=======================================
  Hits          109      109           
  Misses          1        1           

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