chore: upgrade vite-plus

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

[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 performs a comprehensive dependency update, with a central focus on upgrading the vite-plus framework to its most recent development iteration. This ensures the project leverages the latest improvements and fixes from the framework. Alongside this, numerous other packages, including essential utilities and development tools, have been brought up to date. A specific configuration path for the oxlint linter was also rectified to maintain a robust and accurate code analysis setup.

Highlights

• Vite-Plus Upgrade: The primary change involves upgrading the vite-plus framework to its latest development version, indicated by a new commit hash in the pnpm-lock.yaml.
• Dependency Updates: Several key dependencies have been updated, including qs to 6.14.1, undici to 7.18.2, and @types/node to 22.19.7. Additionally, various transitive dependencies related to formatting and linting tools like oxfmt, oxlint, and lightningcss have received significant version bumps.
• Oxlint Configuration Fix: The vite.config.ts file has been updated to correct the extends path for the oxlint configuration, resolving a path resolution issue and ensuring proper linting setup.
• New Transitive Dependency: A new transitive dependency, tinypool@2.0.0, has been introduced, likely as a requirement for one of the updated core packages like oxfmt.

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

[pkg-pr-new]

Open in StackBlitz

npm i https://pkg.pr.new/node-modules/urllib@647

commit: 45d270e

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 92.77%. Comparing base (3732608) to head (45d270e).
⚠️ Report is 2 commits behind head on master.

Additional details and impacted files

@@           Coverage Diff           @@
##           master     #647   +/-   ##
=======================================
  Coverage   92.77%   92.77%           
=======================================
  Files          10       10           
  Lines         747      747           
  Branches      233      233           
=======================================
  Hits          693      693           
  Misses         51       51           
  Partials        3        3           

☔ 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 primarily focuses on upgrading various dependencies, including qs, undici, @types/node, vite-plus, oxfmt, oxlint-tsgolint, oxlint, lightningcss, eventemitter3, and which-typed-array. The pnpm-lock.yaml file has been updated accordingly to reflect these changes and their transitive dependencies. Additionally, the vite.config.ts file includes a minor adjustment to the oxlint configuration path and the removal of a $schema reference in the fmt configuration.

[gemini-code-assist]

The $schema property for fmt configuration has been removed. While this might be intentional due to changes in vite-plus or oxfmt's configuration handling, it's good practice to ensure that removing schema references doesn't lead to a loss of validation or IDE support for the configuration. Could you please confirm if this removal is expected with the vite-plus upgrade and if there are any implications?