From e32855d9e109f998937a06928d5feaec5751bd92 Mon Sep 17 00:00:00 2001 From: MK Date: Wed, 15 Apr 2026 14:44:55 +0800 Subject: [PATCH] chore: upgrade vite-plus to 0.1.18-alpha.0 --- AGENTS.md | 18 +- pnpm-lock.yaml | 882 +++++++++++++++++++++----------------------- pnpm-workspace.yaml | 10 +- 3 files changed, 450 insertions(+), 460 deletions(-) diff --git a/AGENTS.md b/AGENTS.md index 1621c0367..d47e4b4d2 100644 --- a/AGENTS.md +++ b/AGENTS.md @@ -575,12 +575,24 @@ These commands map to their corresponding tools. For example, `vp dev --port 300 ## Common Pitfalls - **Using the package manager directly:** Do not use pnpm, npm, or Yarn directly. Vite+ can handle all package manager operations. -- **Always use Vite commands to run tools:** Don't attempt to run `vp vitest` or `vp oxlint`. They do not exist. Use `vp test`, `vp lint`, and `vp check` instead. -- **Running scripts:** Vite+ commands take precedence over `package.json` scripts. If there is a `test` script defined in `scripts` that conflicts with the built-in `vp test` command, run it using `vp run test`. +- **Always use Vite commands to run tools:** Don't attempt to run `vp vitest` or `vp oxlint`. They do not exist. Use `vp test` and `vp lint` instead. +- **Running scripts:** Vite+ built-in commands (`vp dev`, `vp build`, `vp test`, etc.) always run the Vite+ built-in tool, not any `package.json` script of the same name. To run a custom script that shares a name with a built-in command, use `vp run