refactor!: replace @voidzero-dev/vite-plus-test with upstream vitest (#1588)

## Summary

Deletes the bundled `@voidzero-dev/vite-plus-test` wrapper and consumes
upstream `vitest@4.1.5` (plus `@vitest/browser*`) directly. The vite
redirection role that drove the wrapper is now handled cleanly by
package-manager overrides (`vite` → `@voidzero-dev/vite-plus-core`), so
the bundle was dead weight that lagged upstream releases.

**Public API contract preserved:**
- `vite-plus/test*` IS the public test API — existing user code (`import
{ vi } from 'vite-plus/test'`, etc.) is NEVER rewritten.
- New vite-plus users don't install `vitest` or `@vitest/*` separately;
they come in transitively as direct deps of `vite-plus`.
- `vp migrate` on an upstream-vitest project still forward-migrates
`vitest`, `vitest/*`, `@vitest/browser*`, declare-module specifiers, and
`/// <reference types>` directives to the `vite-plus/test*` surface
(one-time transition).

**Notable changes:**
- `packages/cli/build.ts`: `syncTestPackageExports` auto-generates
`./test/*` shims from upstream `vitest`'s exports map, plus
`./test/<provider>` and `./test/browser/providers/<short>` shims
projected from each `@vitest/browser-*` package's exports.
- `packages/cli/package.json`: adds `@vitest/browser`,
`@vitest/browser-playwright`, `@vitest/browser-preview`,
`@vitest/browser-webdriverio` as direct catalog deps pinned to `4.1.5`.
- `crates/vite_global_cli/src/commands/version.rs`: vitest ToolSpec
points at the `vitest` package directly.
- `packages/cli/src/resolve-test.ts`: resolves `vitest/package.json` and
reads `bin.vitest` so `vp test` invokes upstream vitest.
- `packages/cli/src/utils/constants.ts`: drops `vitest` from
`VITE_PLUS_OVERRIDE_PACKAGES`; only `vite` remains a managed key.
- `packages/cli/src/migration/migrator.ts`:
- Adds an `isVitestAdjacent` flag that flips `needVitePlus = true` for
projects with packages like `vitest-browser-svelte` even when there's no
vite/oxlint/tsdown to migrate.
- Adds `pruneLegacyWrapperAliases` / `pruneYamlMapLegacyWrapperAliases`
sweeps that rewrite stale `vitest: npm:@voidzero-dev/vite-plus-test@*`
aliases to `^4.1.5` (so existing `catalog:` refs keep resolving) and
drop other stale wrapper-targeted keys.
- `packages/cli/src/migration/bin.ts`: adds a `handleInstallResult`
helper so failed reinstalls warn the user, append to `report.warnings`,
and flip `process.exitCode` instead of being silently reported as
success.

## User-visible behavior changes

`vp test -h` and live test runs now show vitest's native banner
(`vitest/<semver>`, ` RUN v<semver> <cwd>`) instead of the
wrapper-rebranded output (`vp test/<semver>`, ` RUN <cwd>`). This is the
tradeoff for delegating directly to upstream vitest without a wrapper
layer.

## Test plan

- [x] `cargo test -p vite_migration --lib`: 167 tests pass
- [x] `pnpm exec vitest run` (packages/cli): 374 tests pass
- [x] `pnpm bootstrap-cli` succeeds
- [x] `pnpm -F vite-plus snap-test-global` + `snap-test-local`: all
fixtures regenerated; diffs only reflect expected behavior (forward
import rewrites, `@vitest/browser*` removed from user devDeps,
`playwright`/`webdriverio` preserved as peers, stale `vite-plus-test`
catalog aliases normalized to `^4.1.5`).
- [ ] Manual end-to-end: `vp test` on a fixture using `import { vi }
from 'vite-plus/test'`; `vi.mock(...)`. See "Follow-up" below.
- [ ] Manual end-to-end: `vp migrate` on a fresh upstream-vitest
project.
- [ ] `pnpm install` clean: zero `@voidzero-dev/vite-plus-test`
references in the lockfile, browser-provider packages installed
transitively via `vite-plus`.

## Follow-up

- vitest-dev/vitest#10489

🤖 Generated with [Claude Code](https://claude.com/claude-code)


<!-- CURSOR_SUMMARY -->
---

> [!NOTE]
> **Medium Risk**
> Touches release/publish paths, daily dep bumps, and CI override
behavior for all package managers (especially Bun peer resolution).
Public migration guidance and version reporting change, but the
`vite-plus/test*` import surface stays the same.
> 
> **Overview**
> Removes **`@voidzero-dev/vite-plus-test`** from release, pkg.pr.new,
and CI pack flows, and stops bumping **`packages/test`** in
**`upgrade-deps`** and prepare-release. Vitest is now tracked as
upstream **`vitest`** with catalog **`@vitest/*`** entries kept on the
same exact version.
> 
> **Dependency automation** rewrites **`VITEST_VERSION`**,
**`test-vp-create`** override pins, and README manual-migration
**`vitest`** literals (exact semver instead of
**`npm:@voidzero-dev/vite-plus-test@latest`**).
**`pnpm-workspace.yaml`** matching switches from the old
**`vitest-dev`** alias to a plain **`vitest:`** catalog line.
> 
> **CI packaging** pins **`core`/`cli`** to **`0.0.0`** for stable tgz
names, drops the test package tarball, and adds **`repack-vite-tgz`** so
Bun smoke/e2e can satisfy Vitest’s **`peer vite`** via a masqueraded
**`vite-7.99.0.tgz`**. **`vp create`** tests override
**`vitest`/`@vitest/*`** by version instead of a local test tgz.
> 
> **User-facing docs and CLI**: README explains pinning bundled Vitest
for a single copy with **`vp test`**. **`vp --version`** resolves Vitest
from the **`vitest`** package. Migration file walking adds
**`.cjs`/`.cts`** for reverse **`require('vite-plus/test/...')`**
rewrites.
> 
> <sup>Reviewed by [Cursor Bugbot](https://cursor.com/bugbot) for commit
9b59731. Bugbot is set up for automated
code reviews on this repo. Configure
[here](https://www.cursor.com/dashboard/bugbot).</sup>
<!-- /CURSOR_SUMMARY -->

---------

Co-authored-by: Claude Opus 4.7 <noreply@anthropic.com>

Author: Brooooooklyn

.github/scripts/upgrade-deps.ts

@@ -152,13 +152,41 @@ async function updatePnpmWorkspace(versions: PnpmWorkspaceVersions): Promise<voi
   let content = fs.readFileSync(filePath, 'utf8');
 
   // oxlint's trailing \n in the pattern disambiguates from oxlint-tsgolint.
+  // All @vitest/* catalog entries (browser + core direct deps) must stay pinned
+  // to the same exact version as `vitest` itself, otherwise the catalog drifts
+  // from VITEST_VERSION.
+  const vitestExactVersionPackages = [
+    '@vitest/browser',
+    '@vitest/browser-playwright',
+    '@vitest/browser-preview',
+    '@vitest/browser-webdriverio',
+    '@vitest/expect',
+    '@vitest/mocker',
+    '@vitest/pretty-format',
+    '@vitest/runner',
+    '@vitest/snapshot',
+    '@vitest/spy',
+    '@vitest/utils',
+  ];
+  const vitestExactVersionEntries: PnpmWorkspaceEntry[] = vitestExactVersionPackages.map((pkg) => ({
+    name: pkg,
+    pattern: new RegExp(`'${pkg.replaceAll('/', '\\/')}': ([\\d.]+(?:-[\\w.]+)?)`),
+    replacement: `'${pkg}': ${versions.vitest}`,
+    newVersion: versions.vitest,
+  }));
   const entries: PnpmWorkspaceEntry[] = [
     {
       name: 'vitest',
-      pattern: /vitest-dev: npm:vitest@\^([\d.]+(?:-[\w.]+)?)/,
-      replacement: `vitest-dev: npm:vitest@^${versions.vitest}`,
+      // The `@voidzero-dev/vite-plus-test` wrapper (which used to be aliased
+      // here via `vitest-dev: npm:vitest@^…`) has been removed. Vitest is now
+      // a plain catalog entry pinned to an exact version (`vitest: x.y.z`),
+      // so match that shape directly. The leading newline anchor disambiguates
+      // from neighbouring keys like `vitepress-*` and `@vitest/browser`.
+      pattern: /\n {2}vitest: ([\d.]+(?:-[\w.]+)?)\n/,
+      replacement: `\n  vitest: ${versions.vitest}\n`,
       newVersion: versions.vitest,
     },
+    ...vitestExactVersionEntries,
     {
       name: 'tsdown',
       pattern: /tsdown: \^([\d.]+(?:-[\w.]+)?)/,
@@ -246,34 +274,129 @@ async function updatePnpmWorkspace(versions: PnpmWorkspaceVersions): Promise<voi
   console.log('Updated pnpm-workspace.yaml');
 }
 
-// ============ Update packages/test/package.json ============
-async function updateTestPackage(vitestVersion: string): Promise<void> {
-  const filePath = path.join(ROOT, 'packages/test/package.json');
-  const pkg: PackageJson = readJsonFile(filePath);
-  const devDependencies = pkg.devDependencies;
-  if (!devDependencies) {
-    throw new Error('packages/test/package.json is missing devDependencies');
+// ============ Update VITEST_VERSION constant ============
+// Keeps the TypeScript source-of-truth (`packages/cli/src/utils/constants.ts`)
+// in sync with the `vitest:` catalog entry in pnpm-workspace.yaml. The
+// constant is consumed by both `packages/cli` and `ecosystem-ci/patch-project.ts`
+// (which re-imports it), so daily upstream bumps must update it here too.
+async function updateVitestVersionConstant(vitestVersion: string): Promise<void> {
+  const filePath = path.join(ROOT, 'packages/cli/src/utils/constants.ts');
+  const content = fs.readFileSync(filePath, 'utf8');
+  const pattern = /export const VITEST_VERSION = '([\d.]+(?:-[\w.]+)?)';/;
+  let oldVersion: string | undefined;
+  const updated = content.replace(pattern, (_match: string, captured: string) => {
+    oldVersion = captured;
+    return `export const VITEST_VERSION = '${vitestVersion}';`;
+  });
+  if (oldVersion === undefined) {
+    throw new Error(
+      `Failed to match VITEST_VERSION in ${filePath} — the pattern ${pattern} is stale, ` +
+        `please update it in .github/scripts/upgrade-deps.ts`,
+    );
   }
+  fs.writeFileSync(filePath, updated);
+  recordChange('VITEST_VERSION constant', oldVersion, vitestVersion);
+  console.log('Updated packages/cli/src/utils/constants.ts');
+}
 
-  // Update all @vitest/* devDependencies
-  for (const dep of Object.keys(devDependencies)) {
-    if (dep.startsWith('@vitest/')) {
-      devDependencies[dep] = vitestVersion;
+// ============ Update .github/workflows/test-vp-create.yml ============
+// The `vp create` smoke-test workflow pins every vitest-family package via the
+// `VP_OVERRIDE_PACKAGES` env var so that template installs use the bundled
+// version. Daily upstream bumps must rewrite those pins so the workflow does
+// not drift behind the rest of the repo.
+async function updateTestVpCreateWorkflow(vitestVersion: string): Promise<void> {
+  const filePath = path.join(ROOT, '.github/workflows/test-vp-create.yml');
+  const content = fs.readFileSync(filePath, 'utf8');
+  const vitestKeys = [
+    'vitest',
+    '@vitest/expect',
+    '@vitest/runner',
+    '@vitest/snapshot',
+    '@vitest/spy',
+    '@vitest/utils',
+    '@vitest/mocker',
+    '@vitest/pretty-format',
+    '@vitest/coverage-v8',
+    '@vitest/coverage-istanbul',
+  ];
+  let updated = content;
+  let oldVersion: string | undefined;
+  for (const key of vitestKeys) {
+    const pattern = new RegExp(`"${key.replaceAll('/', '\\/')}":"([\\d.]+(?:-[\\w.]+)?)"`);
+    let matched = false;
+    updated = updated.replace(pattern, (_match: string, captured: string) => {
+      matched = true;
+      oldVersion ??= captured;
+      return `"${key}":"${vitestVersion}"`;
+    });
+    if (!matched) {
+      throw new Error(
+        `Failed to match "${key}" in ${filePath} — the pattern ${pattern} is stale, ` +
+          `please update it in .github/scripts/upgrade-deps.ts`,
+      );
     }
   }
+  fs.writeFileSync(filePath, updated);
+  recordChange('test-vp-create workflow', oldVersion ?? null, vitestVersion);
+  console.log('Updated .github/workflows/test-vp-create.yml');
+}
 
-  // Update vitest-dev devDependency
-  if (devDependencies['vitest-dev']) {
-    devDependencies['vitest-dev'] = `^${vitestVersion}`;
-  }
-
-  // Update @vitest/ui peerDependency if present
-  if (pkg.peerDependencies?.['@vitest/ui']) {
-    pkg.peerDependencies['@vitest/ui'] = vitestVersion;
+// ============ Update README.md manual-migration vitest pins ============
+// The manual-migration guide pins `vitest` to an exact version in three places —
+// the npm/Bun `overrides` block, the pnpm-workspace `overrides` block, and the
+// Yarn `resolutions` block — so a hand-migrated project shares one Vitest copy
+// with the bundled `vp test`. Those literals are NOT interpolated from
+// VITEST_VERSION, so a daily bump must rewrite them or the guide drifts behind the
+// bundled version. The packages/cli/README.md mirror (refreshed from the root
+// README's suffix at build time) is kept in sync here too so the daily PR stays
+// self-consistent without depending on a build step running first.
+async function updateReadmeVitestPins(vitestVersion: string): Promise<void> {
+  const readmePaths = [path.join(ROOT, 'README.md'), path.join(ROOT, 'packages/cli/README.md')];
+  // JSON form: `"vitest": "4.1.9"` — npm/Bun `overrides` + Yarn `resolutions` (2 blocks)
+  const jsonPattern = /("vitest": ")[\d.]+(?:-[\w.]+)?(")/g;
+  // YAML form: `  vitest: 4.1.9` — pnpm-workspace `overrides` (1 block)
+  const yamlPattern = /(\n\s*vitest: )[\d.]+(?:-[\w.]+)?(\n)/g;
+  // Both READMEs carry the same three manual-migration pins (the cli copy mirrors the
+  // root's suffix). Assert the exact shape so a daily run fails loudly — like every
+  // other updater here — if a block is reworded or removed, instead of silently
+  // shipping a README where only some pins were bumped.
+  const EXPECTED_JSON = 2;
+  const EXPECTED_YAML = 1;
+  let oldVersion: string | undefined;
+  const capture = (match: string): void => {
+    const found = /(\d[\d.]*(?:-[\w.]+)?)/.exec(match)?.[1];
+    if (found && oldVersion === undefined) {
+      oldVersion = found;
+    }
+  };
+  for (const filePath of readmePaths) {
+    if (!fs.existsSync(filePath)) {
+      continue;
+    }
+    const content = fs.readFileSync(filePath, 'utf8');
+    let jsonMatched = 0;
+    let yamlMatched = 0;
+    let updated = content.replace(jsonPattern, (match: string, pre: string, post: string) => {
+      jsonMatched++;
+      capture(match);
+      return `${pre}${vitestVersion}${post}`;
+    });
+    updated = updated.replace(yamlPattern, (match: string, pre: string, post: string) => {
+      yamlMatched++;
+      capture(match);
+      return `${pre}${vitestVersion}${post}`;
+    });
+    if (jsonMatched !== EXPECTED_JSON || yamlMatched !== EXPECTED_YAML) {
+      throw new Error(
+        `Expected ${EXPECTED_JSON} JSON + ${EXPECTED_YAML} YAML vitest pins in ${filePath}, ` +
+          `found ${jsonMatched} + ${yamlMatched} — the manual-migration section changed, ` +
+          `please update updateReadmeVitestPins in .github/scripts/upgrade-deps.ts`,
+      );
+    }
+    fs.writeFileSync(filePath, updated);
+    console.log(`Updated ${path.relative(ROOT, filePath)}`);
   }
-
-  fs.writeFileSync(filePath, JSON.stringify(pkg, null, 2) + '\n');
-  console.log('Updated packages/test/package.json');
+  recordChange('README vitest pins', oldVersion ?? null, vitestVersion);
 }
 
 // ============ Update packages/core/package.json ============
@@ -430,7 +553,9 @@ await updatePnpmWorkspace({
   oxcParser: oxcParserVersion,
   oxcTransform: oxcTransformVersion,
 });
-await updateTestPackage(vitestVersion);
+await updateVitestVersionConstant(vitestVersion);
+await updateTestVpCreateWorkflow(vitestVersion);
+await updateReadmeVitestPins(vitestVersion);
 await updateCorePackage(devtoolsVersion);
 
 writeMetaFiles();

.github/workflows/e2e-test.yml

@@ -109,9 +109,32 @@ jobs:
       - name: Pack packages into tgz
         run: |
           mkdir -p tmp/tgz
+          # Every tgz consumer below references fixed `*-0.0.0.tgz` filenames.
+          # A release commit can leave `packages/{core,cli}` at a published
+          # version (e.g. 0.1.22), which would make `pnpm pack` emit
+          # `*-0.1.22.tgz` instead. Pin both to 0.0.0 so the names stay stable.
+          (cd packages/core && npm pkg set version=0.0.0)
+          (cd packages/cli && npm pkg set version=0.0.0)
           cd packages/core && pnpm pack --pack-destination ../../tmp/tgz && cd ../..
-          cd packages/test && pnpm pack --pack-destination ../../tmp/tgz && cd ../..
           cd packages/cli && pnpm pack --pack-destination ../../tmp/tgz && cd ../..
+          # Bun is uniquely strict about peer-dep resolution:
+          #   1. It checks the *resolved target's* package name and version
+          #      against the peer range (vitest 4.1.9 declares peer
+          #      `vite ^6 || ^7 || ^8`).
+          #   2. A file: override pointing at the vite-plus-core tgz fails
+          #      both the name check (target is `@voidzero-dev/vite-plus-core`,
+          #      not `vite`) and the version check (0.0.0 is outside `^6|^7|^8`).
+          # pnpm/npm/yarn don't enforce either, and using the same core tgz as
+          # the file: target for both `vite` and `@voidzero-dev/vite-plus-core`
+          # is the only configuration they install cleanly. See
+          # https://github.com/oven-sh/bun/issues/8406.
+          #
+          # Generate a sibling vite-7.99.0.tgz: a copy of the core tgz with
+          # `package.json#name` rewritten to "vite" and `version` to 7.99.0.
+          # ecosystem-ci/patch-project.ts points its vite override at this
+          # tgz only for bun-based projects (e.g. bun-vite-template); pnpm-,
+          # npm- and yarn-based ecosystem projects use the real core tgz.
+          pnpm exec tool repack-vite-tgz tmp/tgz/voidzero-dev-vite-plus-core-0.0.0.tgz tmp/tgz/vite-7.99.0.tgz vite 7.99.0
           # Copy vp binary for e2e-test job (findVpBinary expects it in target/)
           cp target/${{ matrix.target }}/release/vp tmp/tgz/vp 2>/dev/null || cp target/${{ matrix.target }}/release/vp.exe tmp/tgz/vp.exe 2>/dev/null || true
           cp target/${{ matrix.target }}/release/vp-shim.exe tmp/tgz/vp-shim.exe 2>/dev/null || true

.github/workflows/prepare_release.yml

@@ -54,7 +54,6 @@ jobs:
           }
           update_json packages/cli/package.json
           update_json packages/core/package.json
-          update_json packages/test/package.json
           update_toml packages/cli/binding/Cargo.toml
           update_toml crates/vite_global_cli/Cargo.toml
 

.github/workflows/publish-to-pkg.pr.new.yml

@@ -136,5 +136,4 @@ jobs:
             './packages/cli/cli-npm/*' \
             './packages/cli' \
             './packages/core' \
-            './packages/prompts' \
-            './packages/test'
+            './packages/prompts'

.github/workflows/release.yml

@@ -161,7 +161,6 @@ jobs:
       - name: Publish
         run: |
           pnpm publish --filter=./packages/core --tag latest --access public --no-git-checks
-          pnpm publish --filter=./packages/test --tag latest --access public --no-git-checks
           pnpm publish --filter=./packages/cli --tag latest --access public --no-git-checks
 
       - name: Create release body
@@ -177,7 +176,6 @@ jobs:
           ### Published Packages
 
           - \`@voidzero-dev/vite-plus-core@${VERSION}\`
-          - \`@voidzero-dev/vite-plus-test@${VERSION}\`
           - \`vite-plus@${VERSION}\`
 
           ### Installation
@@ -228,7 +226,6 @@ jobs:
 
             **Published Packages:**
             • @voidzero-dev/vite-plus-core@${{ env.VERSION }}
-            • @voidzero-dev/vite-plus-test@${{ env.VERSION }}
             • vite-plus@${{ env.VERSION }}
 
             **Install:**

.github/workflows/test-vp-create.yml

@@ -95,9 +95,34 @@ jobs:
       - name: Pack packages into tgz
         run: |
           mkdir -p tmp/tgz
+          # Every tgz consumer below references fixed `*-0.0.0.tgz` filenames.
+          # A release commit can leave `packages/{core,cli}` at a published
+          # version (e.g. 0.1.22), which would make `pnpm pack` emit
+          # `*-0.1.22.tgz` instead. Pin both to 0.0.0 so the names stay stable.
+          (cd packages/core && npm pkg set version=0.0.0)
+          (cd packages/cli && npm pkg set version=0.0.0)
           cd packages/core && pnpm pack --pack-destination ../../tmp/tgz && cd ../..
-          cd packages/test && pnpm pack --pack-destination ../../tmp/tgz && cd ../..
           cd packages/cli && pnpm pack --pack-destination ../../tmp/tgz && cd ../..
+          # Bun is uniquely strict about peer-dep resolution:
+          #   1. It checks the *resolved target's* package name and version
+          #      against the peer range (vitest 4.1.9 declares peer
+          #      `vite ^6 || ^7 || ^8`).
+          #   2. A file: override pointing at the vite-plus-core tgz fails
+          #      both the name check (target is `@voidzero-dev/vite-plus-core`,
+          #      not `vite`) and the version check (0.0.0 is outside `^6|^7|^8`).
+          # pnpm/npm/yarn don't enforce either, and using the same core tgz as
+          # the file: target for both `vite` and `@voidzero-dev/vite-plus-core`
+          # is the only configuration they install cleanly. See
+          # https://github.com/oven-sh/bun/issues/8406.
+          #
+          # Generate a sibling vite-7.99.0.tgz: a copy of the core tgz with
+          # `package.json#name` rewritten to "vite" and `version` to 7.99.0.
+          # Only the bun matrix entry below points its vite override at this
+          # alias tgz; pnpm/npm/yarn keep pointing at the real core tgz so
+          # pnpm's workspace resolver doesn't trip on a "vite@<version>"
+          # registry lookup (the renamed tgz makes pnpm register the dep as
+          # vite@7.99.0 and then probe npmjs.org to validate the version).
+          pnpm exec tool repack-vite-tgz tmp/tgz/voidzero-dev-vite-plus-core-0.0.0.tgz tmp/tgz/vite-7.99.0.tgz vite 7.99.0
           # Copy vp binary for test jobs
           cp target/x86_64-unknown-linux-gnu/release/vp tmp/tgz/vp
           ls -la tmp/tgz
@@ -154,6 +179,13 @@ jobs:
           - yarn
           - bun
     env:
+      # Bun's strict peer check requires the `vite` override target's tgz to be
+      # named "vite" with a version satisfying vitest's `peer vite ^6 || ^7 || ^8`.
+      # The bun matrix entry uses the masquerade tgz (vite-7.99.0.tgz). pnpm/npm/yarn
+      # point at the real core tgz — anything else trips a registry lookup for
+      # vite@<version> when sub-package and override targets are both file: tgz aliases.
+      VITE_OVERRIDE_TGZ: ${{ matrix.package-manager == 'bun' && 'vite-7.99.0.tgz' || 'voidzero-dev-vite-plus-core-0.0.0.tgz' }}
+      VP_VERSION: 'file:${{ github.workspace }}/tmp/tgz/vite-plus-0.0.0.tgz'
       # Force full dependency rewriting so the library template's existing
       # vite-plus dep gets overridden with the local tgz
       VP_FORCE_MIGRATE: '1'
@@ -170,22 +202,12 @@ jobs:
           name: vite-plus-packages
           path: tmp/tgz
 
-      - name: Resolve tgz paths
-        run: |
-          CLI_TGZ=$(ls "$GITHUB_WORKSPACE"/tmp/tgz/vite-plus-[0-9]*.tgz | head -n1)
-          CORE_TGZ=$(ls "$GITHUB_WORKSPACE"/tmp/tgz/voidzero-dev-vite-plus-core-[0-9]*.tgz | head -n1)
-          TEST_TGZ=$(ls "$GITHUB_WORKSPACE"/tmp/tgz/voidzero-dev-vite-plus-test-[0-9]*.tgz | head -n1)
-          echo "CLI_TGZ=$CLI_TGZ" >> $GITHUB_ENV
-          echo "VP_VERSION=file:$CLI_TGZ" >> $GITHUB_ENV
-          printf 'VP_OVERRIDE_PACKAGES={"vite":"file:%s","vitest":"file:%s","@voidzero-dev/vite-plus-core":"file:%s","@voidzero-dev/vite-plus-test":"file:%s"}\n' \
-            "$CORE_TGZ" "$TEST_TGZ" "$CORE_TGZ" "$TEST_TGZ" >> $GITHUB_ENV
-
       - name: Install vp CLI
         run: |
           mkdir -p target/release
           cp tmp/tgz/vp target/release/vp
           chmod +x target/release/vp
-          node $GITHUB_WORKSPACE/packages/tools/src/install-global-cli.ts --tgz "$CLI_TGZ"
+          node $GITHUB_WORKSPACE/packages/tools/src/install-global-cli.ts --tgz $GITHUB_WORKSPACE/tmp/tgz/vite-plus-0.0.0.tgz
           echo "$HOME/.vite-plus/bin" >> $GITHUB_PATH
 
       - name: Verify vp installation
@@ -195,6 +217,8 @@ jobs:
 
       - name: Run vp create ${{ matrix.template.name }} with ${{ matrix.package-manager }}
         working-directory: ${{ runner.temp }}
+        env:
+          VP_OVERRIDE_PACKAGES: '{"vite":"file:${{ github.workspace }}/tmp/tgz/${{ env.VITE_OVERRIDE_TGZ }}","@voidzero-dev/vite-plus-core":"file:${{ github.workspace }}/tmp/tgz/voidzero-dev-vite-plus-core-0.0.0.tgz","vitest":"4.1.9","@vitest/expect":"4.1.9","@vitest/runner":"4.1.9","@vitest/snapshot":"4.1.9","@vitest/spy":"4.1.9","@vitest/utils":"4.1.9","@vitest/mocker":"4.1.9","@vitest/pretty-format":"4.1.9","@vitest/coverage-v8":"4.1.9","@vitest/coverage-istanbul":"4.1.9"}'
         run: |
           vp create ${{ matrix.template.create-args }} \
             --no-interactive \
@@ -268,10 +292,9 @@ jobs:
         run: |
           node -e "
             const path = require('path');
-            const expected = require('$GITHUB_WORKSPACE/packages/cli/package.json').version;
             const pkg = require(path.resolve('node_modules/vite-plus/package.json'));
-            if (pkg.version !== expected) {
-              console.error('Expected vite-plus@' + expected + ', got ' + pkg.version);
+            if (pkg.version !== '0.0.0') {
+              console.error('Expected vite-plus@0.0.0, got ' + pkg.version);
               process.exit(1);
             }
             console.log('✓ vite-plus@' + pkg.version + ' installed correctly');

.typos.toml

@@ -4,6 +4,12 @@ PUNICODE = "PUNICODE"
 Jod = "Jod" # Node.js v22 LTS codename
 flate = "flate" # flate2 crate name (gzip/deflate compression)
 
+[default.extend-identifiers]
+# Yarn Plug'n'Play — tokenizer splits `PnP` into the word `Pn`, which typos
+# otherwise wants to autocorrect to `On`. Whitelist the full identifier so
+# the parts aren't tokenized.
+PnP = "PnP"
+
 [files]
 extend-exclude = [
   "**/snap-tests/**/snap.txt",