feat(test): support CLI package path aliases in vendor-aliases plugin

Added support for `@voidzero-dev/vite-plus/test/*` subpath imports in addition
to existing `vitest/*` and `@voidzero-dev/vite-plus-test/*` patterns.

All three import patterns now work:
- `vitest/browser-playwright` (Recommended, requires vitest override)
- `@voidzero-dev/vite-plus-test/browser-playwright` (direct test package)
- `@voidzero-dev/vite-plus/test/browser-playwright` (direct CLI package)

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

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>

Author: Brooooooklyn

packages/test/BUNDLING.md

@@ -108,10 +108,11 @@ For maintainers developing the vitest/vite migration feature, here are the trans
 | `from "vite"`                       | `from "@voidzero-dev/vite-plus-core"`                    |
 | `from "vite/module-runner"`         | `from "@voidzero-dev/vite-plus-core/module-runner"`      |
 
-**Note:** When using pnpm overrides, you have two options for the playwright import:
+**Note:** When using pnpm overrides, you have three options for the playwright import:
 
-- `vitest/browser-playwright` - works when `vitest` is overridden to our package
-- `@voidzero-dev/vite-plus-test/browser-playwright` - always works (direct import)
+- `vitest/browser-playwright` - works when `vitest` is overridden to our package (Recommended)
+- `@voidzero-dev/vite-plus-test/browser-playwright` - direct import from test package
+- `@voidzero-dev/vite-plus/test/browser-playwright` - direct import from CLI package
 
 Importing from `@vitest/browser-playwright` requires an additional override for that specific package.
 
@@ -156,11 +157,14 @@ overrides:
 // Before
 import { playwright } from '@vitest/browser-playwright';
 
-// After - Option 1: Direct import (always works)
+// After - Option 1 (Recommended): Via vitest subpath (works when vitest is overridden)
+import { playwright } from 'vitest/browser-playwright';
+
+// After - Option 2: Direct import from test package
 import { playwright } from '@voidzero-dev/vite-plus-test/browser-playwright';
 
-// After - Option 2: Via vitest subpath (works when vitest is overridden)
-import { playwright } from 'vitest/browser-playwright';
+// After - Option 3: Direct import from CLI package
+import { playwright } from '@voidzero-dev/vite-plus/test/browser-playwright';
 ```
 
 ### Plugin Exports for pnpm Overrides
@@ -327,7 +331,8 @@ This is achieved through:
    - Handles `@vitest/*` imports → resolves to copied `dist/@vitest/` files
    - Handles `vitest/*` subpaths → resolves to dist files (enables `vitest/browser-playwright` usage)
    - Handles `@voidzero-dev/vite-plus-test/*` subpaths → maps to equivalent vitest paths
-   - Intercepts `vitest/browser` → returns virtual module ID for BrowserContext plugin
+   - Handles `@voidzero-dev/vite-plus/test/*` subpaths → maps to equivalent vitest paths (CLI package)
+   - Intercepts `vitest/browser`, `@voidzero-dev/vite-plus-test/browser`, `@voidzero-dev/vite-plus/test/browser` → returns virtual module ID for BrowserContext plugin
 
 ### Key Constants
 

packages/test/build.ts

@@ -1148,9 +1148,10 @@ async function patchVitestBrowserPackage() {
       if (id === '${CORE_PACKAGE_NAME}' || id === 'vite') {
         return { id, external: true };
       }
-      // Handle vitest/browser and @voidzero-dev/vite-plus-test/browser
+      // Handle vitest/browser and package aliases
       // Return virtual module ID so BrowserContext plugin can load it
-      if (id === 'vitest/browser' || id === '@voidzero-dev/vite-plus-test/browser') {
+      // Supports: vitest/browser, @voidzero-dev/vite-plus-test/browser, @voidzero-dev/vite-plus/test/browser
+      if (id === 'vitest/browser' || id === '@voidzero-dev/vite-plus-test/browser' || id === '@voidzero-dev/vite-plus/test/browser') {
         return '\\0vitest/browser';
       }
       // Handle vitest/* subpaths (resolve to our dist files)
@@ -1178,6 +1179,14 @@ async function patchVitestBrowserPackage() {
           return vitestSubpathMap[vitestEquiv];
         }
       }
+      // Handle @voidzero-dev/vite-plus/test/* subpaths (CLI package paths, same as vitest/*)
+      if (id.startsWith('@voidzero-dev/vite-plus/test/')) {
+        const subpath = id.slice('@voidzero-dev/vite-plus/test/'.length);
+        const vitestEquiv = 'vitest/' + subpath;
+        if (vitestSubpathMap[vitestEquiv]) {
+          return vitestSubpathMap[vitestEquiv];
+        }
+      }
       // Handle @vitest/* packages (resolve to our copied files)
       const vendorMap = {
       ${mappingEntries}
@@ -1235,15 +1244,16 @@ async function patchVitestBrowserPackage() {
   }
   console.log('  Removed bundled deps from include list');
 
-  // 4. Patch BrowserContext to also handle @voidzero-dev/vite-plus-test/browser
+  // 4. Patch BrowserContext to also handle our package aliases as fallback
   // This allows direct imports from our package without requiring vitest override
+  // Supports: @voidzero-dev/vite-plus-test/browser, @voidzero-dev/vite-plus/test/browser
   const browserContextPattern = /if \(id === ID_CONTEXT\) \{/;
   if (browserContextPattern.test(content)) {
     content = content.replace(
       browserContextPattern,
-      `if (id === ID_CONTEXT || id === "@voidzero-dev/vite-plus-test/browser") {`,
+      `if (id === ID_CONTEXT || id === "@voidzero-dev/vite-plus-test/browser" || id === "@voidzero-dev/vite-plus/test/browser") {`,
     );
-    console.log('  Patched BrowserContext to handle @voidzero-dev/vite-plus-test/browser');
+    console.log('  Patched BrowserContext to handle package aliases');
   } else {
     console.log('  Warning: Could not find BrowserContext pattern to patch');
   }