perf: uninstall classnames, install clsx

[li-jia-nan]

Summary by CodeRabbit

• 新特性
  • 无
• 重构
  • 将样式类名工具从 classnames 替换为 clsx，保持组件外观与行为不变。
• 杂务
  • 更新依赖与开发工具：替换 classnames 相关类型依赖，新增 TypeScript ESLint 工具，恢复并整理 React/React DOM 对等依赖声明；优化 .gitignore 与文件末尾换行格式。对终端用户无功能或界面变动。

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Preview	Comments	Updated (UTC)
notification	Ready	Preview	Comment	Sep 28, 2025 4:48am

[coderabbitai]

Walkthrough

在依赖层面以 clsx 替代 classnames，并调整相关 TypeScript/ESLint 开发依赖与 peerDependencies 位置；在组件内部将 classNames 调用迁移至 clsx；同时对 .gitignore 做少量格式与条目修正。

Changes

Cohort / File(s)	Summary of Changes
Ignore 清理与规范 \.gitignore	新增 pnpm-lock.yaml 忽略；去除 .env.local 行尾空格；为 bun.lockb 补齐末尾换行。
依赖与配置更新 package.json	将依赖由 classnames 替换为 clsx；移除 @types/classnames，新增 @types/node；补充 @typescript-eslint/eslint-plugin 与 @typescript-eslint/parser；将 peerDependencies 移至文件末尾并恢复 react/react-dom 要求。
组件内样式类辅助库迁移 src/Notice.tsx, src/NoticeList.tsx	从 classnames 切换到 clsx 的导入与调用；保持原逻辑与对外接口不变。

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~10 minutes

Possibly related PRs

• chore: fix eslint #370 — 同步引入相同的 TypeScript ESLint 开发依赖（@typescript-eslint/eslint-plugin 与 @typescript-eslint/parser），依赖层面的直接关联。

Poem

我把耳朵竖成 V，跳过 classnames 的溪
clsx 轻巧又干脆，风吹草低不粘泥
.gitignore 抚平褶，锁文件也合宜
代码园里挖胡萝卜，蹦蹦跳跳合并你 🥕✨

Pre-merge checks and finishing touches

✅ Passed checks (3 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title Check	✅ Passed	该标题使用简洁的句子突出显示了主要变更，即卸载 classnames 并安装 clsx，准确反映了 PR 的核心内容，同时符合常规提交（Conventional Commits）的格式要求，因此能够让读取历史记录的开发者快速了解此次更改的目的和范围。
Docstring Coverage	✅ Passed	No functions found in the changes. Docstring coverage check skipped.

✨ 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 dd83257 and 8078754.

📒 Files selected for processing (4)

• .gitignore (1 hunks)
• package.json (2 hunks)
• src/Notice.tsx (2 hunks)
• src/NoticeList.tsx (1 hunks)

---

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 focuses on a performance optimization by migrating from the classnames library to clsx for dynamically constructing CSS class strings. This change involves updating the project's dependencies and refactoring the relevant source code files to utilize the new utility. Additionally, the .gitignore file has been adjusted to accommodate PNPM lock files, streamlining the development environment.

Highlights

• Dependency Migration: The classnames utility library has been uninstalled and replaced with clsx to potentially improve performance in class name generation.
• Package Configuration Updates: The package.json file has been updated to reflect the dependency change, including the removal of @types/classnames and the addition of @types/node. The peerDependencies block was also relocated.
• Codebase Refactoring: All instances where classnames was used in src/Notice.tsx and src/NoticeList.tsx have been updated to use the new clsx import and function calls.
• Git Ignore Update: The .gitignore file has been updated to include pnpm-lock.yaml, ensuring proper version control for PNPM lock files.

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

[codecov]

Codecov Report

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

Additional details and impacted files

@@            Coverage Diff             @@
##           master     #377      +/-   ##
==========================================
- Coverage   99.74%   99.74%   -0.01%     
==========================================
  Files           7        7              
  Lines         777      775       -2     
  Branches      126      126              
==========================================
- Hits          775      773       -2     
  Misses          2        2              

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

[gemini-code-assist]

Code Review

This pull request replaces classnames with clsx for better performance, which is a welcome improvement. The changes are correctly implemented across package.json and the component files. I have a couple of minor suggestions to ensure consistency in how clsx is imported across the project.