Vite+
Check the Installed Release
Vite+ is pre-1.0 and changes quickly. Before editing:
- Install the repository's locked dependencies.
- Record
pnpm exec vp --version and, when available,
pnpm exec vp toolchain --json.
- Read the relevant packaged documentation under
node_modules/vite-plus/docs/ and any shipped AGENTS.md.
- When upgrading, read the intervening
release notes.
The installed CLI and packaged docs override memorized command, config, action,
hook, and dependency shapes. Carry a workaround only when it reproduces on the
installed version and has a named removal condition.
Target Contract
- For pnpm creation or package-manager upgrades, target pnpm 12 or newer and
pin the selected version. Bootstrap existing projects with their current pin
first; preserve another package manager when migration is outside scope.
- Use the repository-local CLI interactively; no global
vp is required.
Package scripts and CI may use bare vp when their environment provides it.
vite.config.ts owns Vite+, test, lint, format, pack, staged, and task config
supported by the selected release. Remove parallel configs only after
migration proves their settings were preserved.- Tests use the public Vite+ test imports exposed by the installed release.
- Existing release, deploy, SDK generation, native packaging, and consumer
checks remain when Vite+ does not replace them.
- Contributor and agent guidance changes with the commands it documents.
Workflow
- Audit manifests, lockfiles, runtime/package-manager owners, workspace shape,
scripts, configs, tests, hooks, CI, packaging, and release/deploy paths.
- Read bootstrap for creation, first migration, or
target-version upgrades.
- Read exactly one shape reference:
packages for a standalone package or
monorepos for a workspace.
- Run the selected release's migrator before hand-editing generated config.
Reconcile its result with repository-specific boundaries.
- Read commands before changing invocation or task
wiring, testing when tests change, and
hooks only when hook policy changes.
- Read CI before workflow edits.
- Load known issues only after unexpected
behavior reproduces or during an affected upgrade.
- For new config, task-graph, packaging, or CI code, open the closest
maintained example after selecting the repository
shape. Adapt it to the installed Vite+ release; do not copy its pins.
Version Ownership
Preserve one checked-in owner for each layer:
| Layer |
Owner |
| runtime |
existing version file, tool manager, or manifest declaration |
| package manager |
packageManager or devEngines.packageManager; one consistent declaration |
| Vite+ |
dependency, catalog, or lockfile selected by migration |
| bundled Vite/Vitest/Oxc |
migrator-managed alias or override verified through the installed toolchain |
| Actions |
immutable action pin plus repository update policy |
Do not duplicate project versions in workflows when an action can read the
existing owner. Do not hand-maintain a static bundled-version table.
Verification
Use the installed release's documented equivalents of:
- frozen dependency install after the lockfile is final
- combined format, lint, and type checks
- test and configured coverage paths
- build or pack plus downstream consumer proof
- preview, browser, staged, hook, or workspace-task checks only when changed
Inspect manifests, consolidated config, and lockfile importers after migration.
Report retained legacy wiring with its incompatibility and removal condition.
1---2name: vite-plus3description: Create, migrate, or align frontend packages and monorepos on Vite+. Use for Vite+ scaffolding, migration, upgrades, `vp` commands, consolidated Vite/Oxlint/Oxfmt/Vitest configuration, hooks, packaging, or CI. Do not use for non-Vite toolchains or for release, deploy, and runtime behavior Vite+ does not own.4---56# Vite+78## Check the Installed Release910Vite+ is pre-1.0 and changes quickly. Before editing:11121. Install the repository's locked dependencies.132. Record `pnpm exec vp --version` and, when available,14 `pnpm exec vp toolchain --json`.153. Read the relevant packaged documentation under16 `node_modules/vite-plus/docs/` and any shipped `AGENTS.md`.174. When upgrading, read the intervening18 [release notes](https://github.com/voidzero-dev/vite-plus/releases).1920The installed CLI and packaged docs override memorized command, config, action,21hook, and dependency shapes. Carry a workaround only when it reproduces on the22installed version and has a named removal condition.2324## Target Contract2526- For pnpm creation or package-manager upgrades, target pnpm 12 or newer and27 pin the selected version. Bootstrap existing projects with their current pin28 first; preserve another package manager when migration is outside scope.29- Use the repository-local CLI interactively; no global `vp` is required.30 Package scripts and CI may use bare `vp` when their environment provides it.31- `vite.config.ts` owns Vite+, test, lint, format, pack, staged, and task config32 supported by the selected release. Remove parallel configs only after33 migration proves their settings were preserved.34- Tests use the public Vite+ test imports exposed by the installed release.35- Existing release, deploy, SDK generation, native packaging, and consumer36 checks remain when Vite+ does not replace them.37- Contributor and agent guidance changes with the commands it documents.3839## Workflow40411. Audit manifests, lockfiles, runtime/package-manager owners, workspace shape,42 scripts, configs, tests, hooks, CI, packaging, and release/deploy paths.432. Read [bootstrap](references/bootstrap.md) for creation, first migration, or44 target-version upgrades.453. Read exactly one shape reference:46 [packages](references/packages.md) for a standalone package or47 [monorepos](references/monorepos.md) for a workspace.484. Run the selected release's migrator before hand-editing generated config.49 Reconcile its result with repository-specific boundaries.505. Read [commands](references/commands.md) before changing invocation or task51 wiring, [testing](references/testing.md) when tests change, and52 [hooks](references/hooks.md) only when hook policy changes.536. Read [CI](references/ci-cd.md) before workflow edits.547. Load [known issues](references/known-issues.md) only after unexpected55 behavior reproduces or during an affected upgrade.568. For new config, task-graph, packaging, or CI code, open the closest57 [maintained example](references/examples.md) after selecting the repository58 shape. Adapt it to the installed Vite+ release; do not copy its pins.5960## Version Ownership6162Preserve one checked-in owner for each layer:6364| Layer | Owner |65| --- | --- |66| runtime | existing version file, tool manager, or manifest declaration |67| package manager | `packageManager` or `devEngines.packageManager`; one consistent declaration |68| Vite+ | dependency, catalog, or lockfile selected by migration |69| bundled Vite/Vitest/Oxc | migrator-managed alias or override verified through the installed toolchain |70| Actions | immutable action pin plus repository update policy |7172Do not duplicate project versions in workflows when an action can read the73existing owner. Do not hand-maintain a static bundled-version table.7475## Verification7677Use the installed release's documented equivalents of:78791. frozen dependency install after the lockfile is final802. combined format, lint, and type checks813. test and configured coverage paths824. build or pack plus downstream consumer proof835. preview, browser, staged, hook, or workspace-task checks only when changed8485Inspect manifests, consolidated config, and lockfile importers after migration.86Report retained legacy wiring with its incompatibility and removal condition.
uinaf