chore: use Vite+

[fengmk2]

No description provided.

[coderabbitai]

Important

Review skipped

Draft detected.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

---

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

[cloudflare-workers-and-pages]

Deploying egg with    Cloudflare Pages

Latest commit:	8ff913f
Status:	✅  Deploy successful!
Preview URL:	https://e84088a0.egg-cci.pages.dev
Branch Preview URL:	https://vite-plus.egg-cci.pages.dev

View logs

[cloudflare-workers-and-pages]

Deploying egg-v3 with    Cloudflare Pages

Latest commit:	8ff913f
Status:	✅  Deploy successful!
Preview URL:	https://d490640e.egg-v3.pages.dev
Branch Preview URL:	https://vite-plus.egg-v3.pages.dev

View logs

[gemini-code-assist]

Summary of Changes

Hello @fengmk2, 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 orchestrates a significant shift in the project's development workflow by adopting Vite+ as the central toolchain. This change streamlines various development tasks like building, testing, linting, and formatting under a single command-line interface, aiming to simplify configuration and improve consistency across the codebase. The accompanying documentation ensures that developers can quickly adapt to the new system.

Highlights

• Toolchain Migration to Vite+: The project's build, test, linting, and formatting processes have been migrated to use Vite+, a unified toolchain. This involves replacing direct calls to tsdown, oxlint, oxfmt, and vitest with vite CLI commands.
• Dependency Updates: The package.json files across various examples and packages have been updated to remove tsdown and add vite-plus as a dependency. Existing vitest dependencies are retained but their usage is now orchestrated by vite-plus.
• Script Command Refactoring: Build, test, lint, and format scripts in package.json files have been updated to use the vite command (e.g., vite test run, vite lint, vite fmt, vite lib) instead of direct tool invocations.
• Configuration File Changes: Dedicated .oxfmtrc.json and .oxlintrc.json configuration files have been removed, indicating that their functionalities are now managed through Vite+. New vite.config.ts files have been introduced in packages to configure Vite+ for library builds, often integrating existing tsdown.config.ts settings.
• Test File Import Adjustments: Numerous test files have been updated to import testing utilities (like describe, it, expect) from vite-plus/test instead of directly from vitest, aligning with the new unified toolchain approach.
• Documentation Update: The CLAUDE.md file has been significantly updated with a new section detailing the usage, workflow, commands, and common pitfalls of the Vite+ unified toolchain, providing essential guidance for developers.

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 migrates the project's toolchain to Vite+, a unified development tool. The changes are extensive, touching numerous package.json files, test files, and configurations across the monorepo to replace tools like oxlint, oxfmt, tsdown, and vitest with vite-plus commands and imports. The addition of documentation in CLAUDE.md explaining the new workflow is a valuable improvement. The migration appears to be consistently and correctly applied. I have one point of feedback regarding a potential inconsistency between the new documentation and the project's dependencies.

[gemini-code-assist]

The new CLAUDE.md documentation explicitly states that vitest should not be installed directly as vite-plus wraps it:

Do not install Vitest, Oxlint, Oxfmt, or tsdown directly: Vite+ wraps these tools. They must not be installed directly.
...
You must not install vitest to import test utilities.

However, vitest is still listed as a dev dependency here and in other packages. If it's required for type definitions or other reasons not covered by vite-plus, the documentation should be updated to clarify this. If it's not needed, it should be removed to align with the new development guidelines and avoid confusion.