Vite+ 1.0 Released: Unified Frontend Toolchain via vp CLI

Frontend projects often struggle with maintaining multiple tools separately — Node.js versions, test runners, build configurations, and linters each require independent upgrades and compatibility checks. Vite+ 1.0, released by VoidZero on September 28 under the MIT license, aims to consolidate this toolchain into a single, versioned suite.

What the vp CLI Manages

Vite+ builds on Vite, Vitest, Rolldown, Oxc, and tsdown. Its command-line entry point is vp, which provides a consistent interface across the development lifecycle:

vp env — manages Node.js versions (handled by Vite+ itself).

vp create — scaffolds new projects using Vite+ and framework templates.

vp install — installs dependencies via the project's chosen package manager.

vp dev — starts the development server (powered by Vite).

vp check — runs formatting, linting, and type-checking (via Oxfmt, Oxlint, etc.).

vp test — executes tests (via Vitest).

vp build — builds applications (via Vite and Rolldown).

vp pack — builds libraries (via tsdown).

vp run — runs custom tasks with caching (via Vite Task).

All tool configurations are centralized in vite.config.ts at the project root, and common tool dependencies are provided through the vite-plus package. The existing package manager is retained; vp install simply delegates to it.

Configuration and Framework Support

Vite+ is framework-agnostic: it serves React and Vue applications, component libraries, and Node.js CLI projects. Projects do not need to already use Vite. The unified command set means developers can switch between projects without relearning scripts — test, build, and lint entry points are always the same, and custom tasks are invoked via vp run, reducing time spent searching package.json for script names.

Beta to 1.0 Additions

The stable release adds several team-oriented features:

GitLab CI/CD integration via setup-vp.

Homebrew installation and Docker images.

Extended vp migrate support for tsup-based projects. vp toolchain to inspect versions of all built-in tools. vp env doctor to diagnose Node.js and package-manager resolution. vp hooks and vp staged for pre-commit checks on staged files.

These diagnostics are critical: after unifying entry points, teams must still be able to determine exactly which tool versions and environment were used during a failure.

Current Limitations

Remote caching remains on the roadmap. vp release and vp docs are not yet shipped with 1.0, so teams needing those capabilities must keep existing solutions.

Migration Guidance

New projects start with vp create. Existing projects run vp migrate, which rewrites dependencies, imports, and scripts, consolidating configuration into vite.config.ts. The official documentation warns that most projects will still require manual adjustments after migration.

Key caveats:

Vitest 5 breaking changes arrive with Vite+ 1.0. Even projects already on Vite+ must verify test behavior when upgrading. The migrator generates compatibility config; keep it until tests pass, then evaluate removal.

Monorepos must migrate from the workspace root , not individual packages, because package-manager config and lockfiles are shared across the workspace.

Adopt a branch-based workflow: migrate one fully verifiable project, run tests and builds, and for libraries confirm that published artifacts import correctly in consumers. Only after original behavior is preserved should you assess how much dependency and configuration maintenance was actually reduced.