Update Vite+

Updating vite-plus and its related project dependencies. To upgrade the global vp binary, see Upgrading Vite+.

Update with Migrate

The recommended way to update a project is to use vp migrate, which keeps the toolchain dependencies aligned.

After updating the project's vite-plus dependency, run the local CLI to align the toolchain versions:

./node_modules/.bin/vp migrate

If your global CLI is newer than the project's version, running vp migrate upgrades the project to that global version instead:

vp migrate

On a project that is already on Vite+, migrate does a toolchain version upgrade only: it re-pins vite-plus, the vite -> @voidzero-dev/vite-plus-core alias, and the vitest pin to the versions bundled with the CLI running the migration, across every workspace package. It skips the first-time setup steps (git hooks, editor and agent files, lint migration), so a version bump does not re-touch things you already configured. Pass --full to also run that setup.

Manually Updating

Update vite-plus and the vite alias to @voidzero-dev/vite-plus-core together, keeping the core version aligned with vite-plus. Update these entries wherever they are declared in your workspace, including overrides or catalogs, then install dependencies to refresh the lockfile. Also update the Vitest pin to match the bundled version.

Without the global CLI, run the vp commands on this page through your package manager, for example pnpm exec vp toolchain vitest.

Updating the Vitest Pin

If you migrated with vp migrate, your project pins vitest to an exact version so the whole project shares a single Vitest copy with the bundled vp test runner. The pin lives in your package manager's override block:

• npm / Bun: a vitest entry under overrides in package.json
• Yarn: a vitest entry under resolutions in package.json
• pnpm: a vitest@* entry under overrides in pnpm-workspace.yaml. If your package.json already has a pnpm field, the entry lives under pnpm.overrides in package.json instead. pnpm ignores pnpm-workspace.yaml overrides when package.json defines pnpm.overrides.

A Vite+ release can bump the bundled Vitest. Because that pin also applies to vite-plus's own vitest dependency, an out-of-date pin keeps installing the previous runner even after you upgrade vite-plus — splitting Vitest's internals (mocks, expect, runner state) between the pinned copy and the one vp test loads.

After upgrading vite-plus, re-pin vitest to the version Vite+ now bundles. Check that version with:

vp toolchain vitest

Then set the vitest override to that exact version and reinstall dependencies.

Why pnpm overrides use @*

Under pnpm the managed keys use an explicit @* range (vite@*, vitest@*). pnpm applies an override by replacing the declared spec on every manifest, importer manifests included. A bare key matches any spec, including catalog:. The @* range keeps the override on the semver ranges that transitive and peer declarations use, and leaves catalog: references intact. vp up therefore no longer rewrites them to a concrete version.

Preview Builds

After installing a preview build of the global CLI, run migrate in the project to move its local vite-plus onto the same build:

vp migrate

Migrate writes the bridge registry to .npmrc. For Yarn Berry, it writes the registry to .yarnrc.yml. It pins vite-plus and the vite alias to the matching 0.0.0-commit.<sha> version. The vite alias points to @voidzero-dev/vite-plus-core. Commit the registry line if the project CI must test the preview.

After the install, run vp toolchain to show the selected versions. After testing, set vite-plus to latest. Remove the bridge registry line from .npmrc or .yarnrc.yml. Then run vp install.