refactor: replace @voidzero-dev/vite-plus-test with upstream vitest@4.1.5

.github/scripts/upgrade-deps.ts

@@ -152,13 +152,31 @@ async function updatePnpmWorkspace(versions: PnpmWorkspaceVersions): Promise<voi
   let content = fs.readFileSync(filePath, 'utf8');
 
   // oxlint's trailing \n in the pattern disambiguates from oxlint-tsgolint.
+  const vitestBrowserPackages = [
+    '@vitest/browser',
+    '@vitest/browser-playwright',
+    '@vitest/browser-preview',
+    '@vitest/browser-webdriverio',
+  ];
+  const vitestBrowserEntries: PnpmWorkspaceEntry[] = vitestBrowserPackages.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,
     },
+    ...vitestBrowserEntries,
     {
       name: 'tsdown',
       pattern: /tsdown: \^([\d.]+(?:-[\w.]+)?)/,
@@ -246,34 +264,117 @@ 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;
+  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;
+      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);
+  console.log('Updated .github/workflows/test-vp-create.yml');
+}
 
-  // Update vitest-dev devDependency
-  if (devDependencies['vitest-dev']) {
-    devDependencies['vitest-dev'] = `^${vitestVersion}`;
+// ============ Update the @vitest/mocker pnpm patch entry ============
+// `pnpm-workspace.yaml` patches `@vitest/mocker` so the static `vi.mock()`
+// hoister recognizes the public `vite-plus/test` specifier. pnpm keys
+// `patchedDependencies` by EXACT version (`@vitest/mocker@x.y.z`) and errors
+// hard (`ERR_PNPM_PATCHED_PKG_DOES_NOT_MATCH`) when the key drifts from the
+// installed version, so a daily vitest bump would otherwise break every
+// auto-upgrade PR. Rewrite the key + patch-file path and rename the patch file
+// to the new version. The patch file is kept version-suffixed (rather than
+// switching to a name-only key) because its diff context is version-specific:
+// if upstream changes `dist/chunk-hoistMocks.js`, the rename surfaces a loud
+// patch-apply failure that a human must resolve — which is the desired signal.
+async function updateVitestMockerPatch(vitestVersion: string): Promise<void> {
+  const filePath = path.join(ROOT, 'pnpm-workspace.yaml');
+  const content = fs.readFileSync(filePath, 'utf8');
+  const pattern =
+    /'@vitest\/mocker@([\d.]+(?:-[\w.]+)?)': patches\/@vitest__mocker@[\d.]+(?:-[\w.]+)?\.patch/;
+  let oldVersion: string | undefined;
+  const updated = content.replace(pattern, (_match: string, captured: string) => {
+    oldVersion = captured;
+    return `'@vitest/mocker@${vitestVersion}': patches/@vitest__mocker@${vitestVersion}.patch`;
+  });
+  if (oldVersion === undefined) {
+    throw new Error(
+      `Failed to match the @vitest/mocker patchedDependencies entry in ${filePath} — ` +
+        `the pattern ${pattern} is stale, please update it in .github/scripts/upgrade-deps.ts`,
+    );
   }
-
-  // Update @vitest/ui peerDependency if present
-  if (pkg.peerDependencies?.['@vitest/ui']) {
-    pkg.peerDependencies['@vitest/ui'] = vitestVersion;
+  if (oldVersion !== vitestVersion) {
+    const oldPatch = path.join(ROOT, 'patches', `@vitest__mocker@${oldVersion}.patch`);
+    const newPatch = path.join(ROOT, 'patches', `@vitest__mocker@${vitestVersion}.patch`);
+    if (!fs.existsSync(oldPatch)) {
+      throw new Error(
+        `Expected patch file ${oldPatch} to exist before renaming — ` +
+          `the @vitest/mocker patch may have been moved or removed.`,
+      );
+    }
+    fs.renameSync(oldPatch, newPatch);
+    console.log(`Renamed @vitest/mocker patch ${oldVersion} -> ${vitestVersion}`);
   }
-
-  fs.writeFileSync(filePath, JSON.stringify(pkg, null, 2) + '\n');
-  console.log('Updated packages/test/package.json');
+  // Also covers the case where the key version already matches `vitestVersion`
+  // but the value's patch-file suffix had drifted — `content.replace` repaired
+  // the line in memory and we must persist it, otherwise pnpm install can hit
+  // ERR_PNPM_PATCHED_PKG_DOES_NOT_MATCH.
+  if (updated !== content) {
+    fs.writeFileSync(filePath, updated);
+  }
+  recordChange('@vitest/mocker patch', oldVersion, vitestVersion);
 }
 
 // ============ Update packages/core/package.json ============
@@ -430,7 +531,9 @@ await updatePnpmWorkspace({
   oxcParser: oxcParserVersion,
   oxcTransform: oxcTransformVersion,
 });
-await updateTestPackage(vitestVersion);
+await updateVitestVersionConstant(vitestVersion);
+await updateTestVpCreateWorkflow(vitestVersion);
+await updateVitestMockerPatch(vitestVersion);
 await updateCorePackage(devtoolsVersion);
 
 writeMetaFiles();

.github/workflows/e2e-test.yml

@@ -108,9 +108,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.7 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

@@ -93,9 +93,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.7 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
@@ -152,6 +177,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'
@@ -168,22 +200,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
@@ -193,6 +215,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.7","@vitest/expect":"4.1.7","@vitest/runner":"4.1.7","@vitest/snapshot":"4.1.7","@vitest/spy":"4.1.7","@vitest/utils":"4.1.7","@vitest/mocker":"4.1.7","@vitest/pretty-format":"4.1.7","@vitest/coverage-v8":"4.1.7","@vitest/coverage-istanbul":"4.1.7"}'
         run: |
           vp create ${{ matrix.template.create-args }} \
             --no-interactive \
@@ -266,10 +290,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",

README.md

@@ -189,12 +189,11 @@ If you are manually migrating a project to Vite+, install these dev dependencies
 npm install -D vite-plus @voidzero-dev/vite-plus-core@latest
 ```
 
-You need to add overrides to your package manager for `vite` and `vitest` so that other packages depending on Vite and Vitest will use the Vite+ versions:
+You need to add overrides to your package manager for `vite` so that other packages depending on Vite (including Vitest) will use the Vite+ version:
 
 ```json
 "overrides": {
-  "vite": "npm:@voidzero-dev/vite-plus-core@latest",
-  "vitest": "npm:@voidzero-dev/vite-plus-test@latest"
+  "vite": "npm:@voidzero-dev/vite-plus-core@latest"
 }
 ```
 
@@ -203,15 +202,13 @@ If you are using `pnpm`, add this to your `pnpm-workspace.yaml`:
 ```yaml
 overrides:
   vite: npm:@voidzero-dev/vite-plus-core@latest
-  vitest: npm:@voidzero-dev/vite-plus-test@latest
 ```
 
 Or, if you are using Yarn:
 
 ```json
 "resolutions": {
-  "vite": "npm:@voidzero-dev/vite-plus-core@latest",
-  "vitest": "npm:@voidzero-dev/vite-plus-test@latest"
+  "vite": "npm:@voidzero-dev/vite-plus-core@latest"
 }
 ```