From 0ec98c3de1aa0ac70418a909c8111452d57dc7ce Mon Sep 17 00:00:00 2001 From: MK Date: Fri, 20 Mar 2026 09:57:52 +0800 Subject: [PATCH] chore(deps): update vite-plus and related packages to 0.1.13-alpha.5 --- CLAUDE.md | 69 +++++--- package.json | 12 +- pnpm-lock.yaml | 443 +++++++++++++++++++++++++------------------------ 3 files changed, 279 insertions(+), 245 deletions(-) diff --git a/CLAUDE.md b/CLAUDE.md index 2e82b4b9..e925fbe4 100644 --- a/CLAUDE.md +++ b/CLAUDE.md @@ -87,54 +87,77 @@ Tests use Vitest with: # Using Vite+, the Unified Toolchain for the Web -This project is using Vite+, a modern toolchain built on top of Vite, Rolldown, Vitest, tsdown, Oxlint, and Oxfmt. Vite+ wraps these tools and package manager commands in a single, global CLI called `vite`. Vite+ is distinct from Vite, but it invokes Vite through `vite dev` and `vite build`. +This project is using Vite+, a unified toolchain built on top of Vite, Rolldown, Vitest, tsdown, Oxlint, Oxfmt, and Vite Task. Vite+ wraps runtime management, package management, and frontend tooling in a single global CLI called `vp`. Vite+ is distinct from Vite, but it invokes Vite through `vp dev` and `vp build`. ## Vite+ Workflow -`vite` is a global binary that handles the full development lifecycle. Run `vite help` to print a list of commands and `vite --help` for information about a specific command. +`vp` is a global binary that handles the full development lifecycle. Run `vp help` to print a list of commands and `vp --help` for information about a specific command. + +### Start + +- create - Create a new project from a template +- migrate - Migrate an existing project to Vite+ +- config - Configure hooks and agent integration +- staged - Run linters on staged files +- install (`i`) - Install dependencies +- env - Manage Node.js versions -### Vite+ Commands +### Develop - dev - Run the development server -- build - Build for production +- check - Run format, lint, and TypeScript type checks - lint - Lint code -- test - Run tests - fmt - Format code -- lib - Build library -- new - Create a new monorepo package (in-project) or a new project (global) -- run - Run tasks from `package.json` scripts +- test - Run tests + +### Execute + +- run - Run monorepo tasks +- exec - Execute a command from local `node_modules/.bin` +- dlx - Execute a package binary without installing it as a dependency +- cache - Manage the task cache + +### Build -These commands map to their corresponding tools. For example, `vite dev --port 3000` runs Vite's dev server and works the same as Vite. `vite test` runs JavaScript tests through the bundled Vitest. The versions of individual tools can be checked using `vite --version`. For example, `vite lint --version` prints the bundled Oxlint version, and `vite test --version` prints the bundled Vitest version. This is useful when researching documentation, features, and bugs. +- build - Build for production +- pack - Build libraries +- preview - Preview production build -### Package Manager Commands +### Manage Dependencies Vite+ automatically detects and wraps the underlying package manager such as pnpm, npm, or Yarn through the `packageManager` field in `package.json` or package manager-specific lockfiles. -- install - Install all dependencies, or add packages if package names are provided - add - Add packages to dependencies -- remove - Remove packages from dependencies -- dlx - Execute a package binary without installing it as a dependency -- info - View package information from the registry, including latest versions -- link - Link packages for local development +- remove (`rm`, `un`, `uninstall`) - Remove packages from dependencies +- update (`up`) - Update packages to latest versions +- dedupe - Deduplicate dependencies - outdated - Check for outdated packages +- list (`ls`) - List installed packages +- why (`explain`) - Show why a package is installed +- info (`view`, `show`) - View package information from the registry +- link (`ln`) / unlink - Manage local package links - pm - Forward a command to the package manager -- unlink - Unlink packages -- update - Update packages to their latest versions -- why - Show why a package is installed + +### Maintain + +- upgrade - Update `vp` itself to the latest version + +These commands map to their corresponding tools. For example, `vp dev --port 3000` runs Vite's dev server and works the same as Vite. `vp test` runs JavaScript tests through the bundled Vitest. The version of all tools can be checked using `vp --version`. This is useful when researching documentation, features, and bugs. ## 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 `vite vitest` or `vite oxlint`. They do not exist. Use `vite test` and `vite lint` 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 `vite test` command, run it using `vite 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