VitePlus

Move a frontend repo closer to the stock VitePlus toolchain without blindly deleting repo-specific release or runtime logic. VitePlus is in alpha — verify behavior against installed vp --version and the latest release notes rather than 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@v1; the action owns Node and package-manager bootstrap, then runs vp install, vp check, vp test, vp build
• test files use vite-plus/test (and vite-plus/test/browser/context for browser mode)
• scripts prefer vp test, vp test watch, vp test run --coverage, vp pack, vp build, vp update, and vp run <script> (or vpr <script>) over direct package-manager, raw Vitest, or tsdown wiring
• hooks use vp config, .vite-hooks, and vp staged instead of custom Husky or lint-staged
• single-source config in vite.config.ts: no parallel vitest.config.ts, .oxlintrc*, .oxfmtrc*, or tsdown.config.ts
• contributor docs move to the new vp commands in the same change

Workflow