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
• Updated both root package.json and src-web/package.json
• Updated pnpm.overrides in root package.json

[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 performs a comprehensive dependency upgrade, primarily focusing on vite-plus and its related core and test packages to version 0.1.14-alpha.3. This update propagates across the main and web-specific package.json files and the package-lock.json, ensuring consistency. Additionally, the changes introduce a new pre-commit hook configuration to automate code quality checks on staged files, streamlining the development workflow and maintaining code standards.

Highlights

• Dependency Upgrades: Upgraded vite-plus, @voidzero-dev/vite-plus-core (aliased as vite), and @voidzero-dev/vite-plus-test (aliased as vitest) to version 0.1.14-alpha.3 across the project.
• Pre-commit Hooks Enhancement: Introduced a new vp staged command to the .vite-hooks/pre-commit script and added a staged configuration to vite.config.ts for automated code quality checks on staged files.
• Package-lock.json Updates: Synchronized package-lock.json with the new dependency versions, including updates to various @oxc-project, @oxfmt, @oxlint, and lightningcss related packages, and removed several unused or outdated dependencies.
• Registry Mirror Change: Updated many package resolution URLs in package-lock.json to use https://registry.npmmirror.com/.

🧠 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 dependencies to 0.1.14-alpha.3. The changes correctly pin the new versions in package.json and src-web/package.json, which is a good improvement over using latest. The configuration in vite.config.ts is also updated to leverage the new staged feature. I have one suggestion to improve the pre-commit hook for better efficiency.

[gemini-code-assist]

Running both vp lint (which likely lints the entire project) and vp staged (which seems to lint only staged files) in the pre-commit hook is redundant. This can make commits slower than necessary. It's generally better to only run checks on staged files in a pre-commit hook. I suggest keeping only the vp staged command.

vp staged