chore: upgrade vite-plus to 0.1.20-alpha.4

[fengmk2]

Upgrade vite-plus and related packages to 0.1.20-alpha.4 alpha version.

[pkg-pr-new]

Open in StackBlitz

npm i https://pkg.pr.new/fengmk2/urllib@3

commit: a6bf966

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 94.65%. Comparing base (aa93679) to head (a6bf966).
⚠️ Report is 18 commits behind head on master.

Additional details and impacted files

@@           Coverage Diff           @@
##           master       #3   +/-   ##
=======================================
  Coverage   94.65%   94.65%           
=======================================
  Files          10       10           
  Lines         730      730           
  Branches      228      228           
=======================================
  Hits          691      691           
  Misses         36       36           
  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 updates vite-plus, vitest, and various internal toolchain packages (including @oxc-project, @oxfmt, and @oxlint) to newer versions, specifically moving to the 0.1.20-alpha.4 alpha release. The reviewer expressed concern regarding the use of alpha versions for core dependencies, highlighting the risks of instability and potential breaking changes.

[gemini-code-assist]

Upgrading vite-plus and related packages (like vitest and vite-plus-core) to an alpha version (0.1.20-alpha.4) introduces a risk of instability. Alpha versions are not feature-complete, may contain bugs, and are subject to breaking changes. It is recommended to use stable releases for dependencies. If this upgrade is necessary for specific features or fixes, be aware of the potential for issues and breaking changes in subsequent alpha releases.