chore: replace clsx with classix

[wolfcreative]

What

Replace clsx with classix for internal className composition.

Why

This change switches internal className composition from clsx to classix.

classix is actively maintained and designed with performance in mind.
Unlike clsx, which supports multiple input shapes (objects, arrays, mixed arguments),
classix intentionally limits its API to string-based expressions.

Based on personal experience using Ant Design with Next.js on large projects,
classix was observed to perform better in common usage,
both during development and build time.
This is an observational, real-world finding rather than a synthetic benchmark.

In addition, classix is tiny, dependency-free, and preserves behavior fully
for the current usage in this codebase.

Scope

• Internal refactor only
• No breaking changes
• No runtime behavior changes

Summary by CodeRabbit

Chores

• 升级内部依赖库版本，优化 CSS 类名合并工具，提升代码质量。此次更新涉及核心组件和测试文件的依赖调整，确保更好的性能和兼容性表现。

_{✏️ Tip: You can customize this high-level summary in your review settings.}

[coderabbitai]

📝 Walkthrough

概览

本 PR 将项目中的 CSS 类名合并工具库从 clsx 统一迁移至 classix。涉及更新 package.json 中的依赖声明，以及更新所有组件文件和测试文件中的导入语句和函数调用，保持 API 调用方式不变。

变更

内聚 / 文件	变更摘要
组件库文件 docs/examples/components/Button.tsx, docs/examples/components/Spin.tsx, docs/examples/diff-salt.tsx, docs/examples/layer.tsx	将 clsx 导入替换为 classix，并更新相应的函数调用从 clsx(...) 改为 classix(...)，保持类名合并逻辑不变
依赖配置 package.json	将依赖从 "clsx": "^2.1.1" 替换为 "classix": "^2.2.6"
测试文件 tests/css-variables.spec.tsx, tests/index.spec.tsx, tests/server.spec.tsx	更新导入语句从 clsx 改为 classix，并将所有测试中的函数调用从 clsx(...) 改为 classix(...)

预计代码审查工作量

🎯 1 (简单) | ⏱️ ~5 分钟

• 审查重点：所有变更采用相同的重复模式（导入替换和函数调用更新），无需逐个文件进行复杂的逻辑分析
• 注意事项：确认 classix 库的 API 与 clsx 兼容，函数签名相同

相关 PR

• chore: move rc-util to @rc-componet/util and move classnames to clsx #237：该 PR 同样涉及相同文件的类名工具库替换（从 classnames 迁移至 clsx），与本 PR 形成对应的迁移链路

诗歌

🐰 类名小小的斗转星移，
从 clsx 跳到 classix 的舞蹈，
样式依旧，只改其名，
简洁而优雅，完全无痛，
兔子欢呼，迁移成功！

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	标题简洁明了地总结了主要变更：将 clsx 替换为 classix，与所有文件中的实际代码变更完全一致。
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

✨ Finishing touches

• 📝 Generate docstrings

🧪 Generate unit tests (beta)

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

---

📜 Recent review details

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between e964b75 and 95a0243.

⛔ Files ignored due to path filters (1)

• pnpm-lock.yaml is excluded by !**/pnpm-lock.yaml

📒 Files selected for processing (8)

• docs/examples/components/Button.tsx (2 hunks)
• docs/examples/components/Spin.tsx (2 hunks)
• docs/examples/diff-salt.tsx (2 hunks)
• docs/examples/layer.tsx (2 hunks)
• package.json (1 hunks)
• tests/css-variables.spec.tsx (2 hunks)
• tests/index.spec.tsx (12 hunks)
• tests/server.spec.tsx (2 hunks)

🔇 Additional comments (8)

docs/examples/diff-salt.tsx (1)

3-3: 替换执行正确！

导入语句和使用方式都已正确更新为 classix。所有参数均为字符串类型，符合 classix 的 API 限制。

Also applies to: 52-52

docs/examples/components/Spin.tsx (1)

1-1: LGTM！

从 clsx 迁移到 classix 的改动正确，所有类名参数均为字符串，与 classix 的 API 兼容。

Also applies to: 48-48

tests/server.spec.tsx (1)

2-2: 测试文件更新正确！

测试代码已正确更新为使用 classix。测试执行将验证新库的行为兼容性。

Also applies to: 238-238

docs/examples/layer.tsx (1)

2-2: 改动正确！

类名组合逻辑已成功迁移至 classix，使用方式保持一致。

Also applies to: 52-52

docs/examples/components/Button.tsx (1)

3-3: 更新正确！

Button 组件已正确迁移到 classix。虽然传递了多个类名参数，但均为字符串类型，完全兼容 classix 的 API。

Also applies to: 163-163

tests/css-variables.spec.tsx (1)

3-3: 测试代码更新正确！

CSS 变量测试文件已正确更新为使用 classix，参数使用方式兼容。

Also applies to: 193-193

tests/index.spec.tsx (1)

2-2: 所有测试用例已正确更新！

主测试文件中的所有 classix 调用均已正确迁移。由于此文件包含大量测试用例，测试套件的执行将全面验证 classix 与原 clsx 的行为兼容性。

Also applies to: 240-240, 340-340, 412-412, 535-535, 581-581, 609-609, 656-656, 730-730, 810-810, 860-860, 908-908

package.json (1)

49-49: 建议将 classix 更新至最新版本 2.2.4

当前 package.json 中指定的 classix@^2.2.6 版本可能存在问题。npm 官方注册表显示 classix 最新发布版本为 2.2.4。建议检查版本号是否输入正确，并考虑更新至最新版本以获得最新的维护和改进。

从安全性角度：Snyk 数据库中未发现 classix 包有直接漏洞，且该包已被扫描并确认没有已知安全问题。

---

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 @wolfcreative, 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 undertakes an internal refactor to swap the clsx utility with classix for managing CSS class names. The motivation stems from classix's superior performance characteristics, active development, and a more focused API that primarily handles string-based class expressions. This modification is designed to be non-disruptive, preserving all existing functionality and runtime behavior while aiming for efficiency gains.

Highlights

• Dependency Replacement: The clsx utility for composing CSS class names has been replaced with classix across the codebase.
• Performance Improvement: classix is chosen for its active maintenance, performance-oriented design, and observed better real-world performance compared to clsx.
• API Simplification: classix intentionally limits its API to string-based expressions, which aligns with the current usage patterns and simplifies className handling.
• Minimal Impact: This change is an internal refactor with no breaking changes or alterations to runtime behavior, ensuring existing functionality remains intact.

🧠 New Feature in Public Preview: You can now enable Memory to help Gemini Code Assist learn from your team's feedback. This makes future code reviews more consistent and personalized to your project's style. Click here to enable Memory in your admin console.

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
	classix@​2.2.6

View full report

[gemini-code-assist]

Code Review

This pull request successfully replaces the clsx library with classix for constructing CSS class names. The rationale for this change, focusing on performance improvements and active maintenance of classix, is well-articulated. The replacement has been executed correctly and consistently across all relevant files, including the necessary update in package.json. The new classix library is used with string arguments, which aligns with its API and ensures that the behavior remains unchanged. This is a solid refactoring that should bring the intended performance benefits.