feat(deps): upgrade vite-plus to 0.1.14-alpha.3

[fengmk2]

Summary

• Upgrade vite-plus to 0.1.14-alpha.3
• Upgrade @voidzero-dev/vite-plus-core (aliased as vite) to 0.1.14-alpha.3
• Upgrade @voidzero-dev/vite-plus-test (aliased as vitest) to 0.1.14-alpha.3
• Update pnpm overrides to match

[gemini-code-assist]

Summary of Changes

Hello, 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 maintaining the project's dependencies by upgrading vite-plus and its associated packages to their latest alpha release. This ensures the project benefits from the newest features, bug fixes, and performance improvements offered by these updated libraries, and keeps the dependency tree healthy and current.

Highlights

• Dependency Upgrades: The vite-plus package has been upgraded to version 0.1.14-alpha.3. This includes its aliased core (@voidzero-dev/vite-plus-core) and test (@voidzero-dev/vite-plus-test) components.
• PNPM Overrides and Lockfile: The pnpm overrides for vite and vitest have been updated to reflect the new 0.1.14-alpha.3 versions. The pnpm-lock.yaml file has been comprehensively updated to reflect these changes, including numerous transitive dependency bumps for related packages like @oxc-project, @oxfmt, and @oxlint.
• Tooling Updates: Several development tools and their bindings, such as oxfmt, oxlint-tsgolint, oxlint, cac, and tinyexec, have been updated to their latest versions as part of the dependency resolution.

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

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 upgrades vite-plus and its related packages to an alpha version. My main concern is the use of a pre-release version, which can introduce instability. I've also noted that this upgrade results in multiple versions of @oxc-project/types in the lockfile, which is a potential area for improvement to avoid dependency bloat and potential type conflicts.

[gemini-code-assist]

Upgrading vite-plus, vite (aliased to @voidzero-dev/vite-plus-core), and vitest (aliased to @voidzero-dev/vite-plus-test) to an alpha version (0.1.14-alpha.3) introduces a risk of instability and breaking changes, even in devDependencies. Pre-release versions are not recommended for general use. Consider using stable releases unless you are intentionally testing new features or require a fix that is only available in a pre-release version.

[gemini-code-assist]

The lockfile now includes two versions of @oxc-project/types: 0.115.0 and 0.122.0. Having multiple versions of a package, especially a types package, can increase the size of node_modules and may lead to type conflicts. It would be beneficial to investigate why the older version is retained and try to consolidate to a single version.