vite-plus
Installation
SKILL.md
Vite+
Move a frontend repo closer to the stock Vite+ toolchain while preserving repo-specific release and runtime logic. Vite+ is in beta, but still pre-1.0: verify behavior against installed vp --version, packaged docs under node_modules/vite-plus/docs/, and the latest release notes instead of relying on memorized command shapes.
Migration Targets
Default to this destination unless a repo-specific boundary clearly blocks it. If you keep an old command shape, document the reason.
- CI uses
voidzero-dev/setup-vp; the action owns Node and package-manager bootstrap. Let its defaultrun-install: truerunvp install, then runvp check,vp test, andvp build; setrun-install: falseonly when the workflow needs an explicit install step. In repos that pin GitHub Actions, pinsetup-vpto a full commit SHA with a same-line exact version comment and let Dependabot maintain it - Tooling versions have one checked-in source of truth. Node comes from
.node-version; package-manager versions come frompackage.json#packageManager; Vite+ comes from the repo'svite-plusdependency or workspace catalog. Do not repeat Node, pnpm, or Vite+ literals in workflows when a source file can be read - test files use
vite-plus/test(andvite-plus/test/browser/contextfor browser mode); Vite+ 0.2.x runs upstream Vitest directly and no longer uses@voidzero-dev/vite-plus-test - scripts prefer
vp dev,vp test,vp test watch,vp test run --coverage,vp pack,vp build,vp preview, andvp run <script>(orvpr <script>) over direct package-manager, raw Vitest, or tsdown wiring - hooks use
vp config,.vite-hooks, andvp stagedas the default hook stack - single-source config in
vite.config.ts: no parallelvitest.config.ts,.oxlintrc*,.oxfmtrc*, ortsdown.config.ts - project agent guidance comes from Vite+ itself when possible:
vp migrate --agent <name>writes the official shortAGENTS.md/CLAUDE.mdblock, and installed projects may expose the same guidance atnode_modules/vite-plus/AGENTS.md - contributor docs move to the new
vpcommands in the same change