`vp test` fails with missing `server` export from `@vitest/browser/context` when using `@storybook/addon-vitest`

[hwld]

Describe the bug

When using @storybook/addon-vitest, vp test fails because the bundled dist/@vitest/browser/context.js does not provide a server export.

Reproduction

https://github.com/hwld/vite-plus-vitest-browser-context-repro/tree/storybook-repro

Steps to reproduce

git clone https://github.com/hwld/vite-plus-vitest-browser-context-repro.git
cd vite-plus-vitest-browser-context-repro
git switch storybook-repro
vp install
vp exec playwright install --with-deps chromium
vp test

It also reproduces on GitHub Actions:
https://github.com/hwld/vite-plus-vitest-browser-context-repro/actions/runs/23379425887/job/68016454899

System Info

VITE+ - The Unified Toolchain for the Web

Environment:
  Version  24.14.0
  Source   lts

Tool Paths:
  node  /Users/hwld/.vite-plus/js_runtime/node/24.14.0/bin/node
  npm   /Users/hwld/.vite-plus/js_runtime/node/24.14.0/bin/npm
  npx   /Users/hwld/.vite-plus/js_runtime/node/24.14.0/bin/npx
VITE+ - The Unified Toolchain for the Web

vp v0.1.13

Local vite-plus:
  vite-plus  v0.1.13

Tools:
  vite             v8.0.1
  rolldown         v1.0.0-rc.10
  vitest           v4.1.0
  oxfmt            v0.41.0
  oxlint           v1.56.0
  oxlint-tsgolint  v0.17.1
  tsdown           v0.21.4

Environment:
  Package manager  pnpm v10.32.1
  Node.js          v24.14.0

Used Package Manager

pnpm

Logs

SyntaxError: The requested module '.../@voidzero-dev/vite-plus-test/dist/@vitest/browser/context.js' does not provide an export named 'server'

Validations

• Read the Contributing Guidelines.
• Check that there isn't already an issue for the same bug.
• Confirm this is a Vite+ issue and not an upstream issue (Vite, Vitest, tsdown, Rolldown, or Oxc).
• The provided reproduction is a minimal reproducible example.

[claude]

Analysis

Root Cause

The issue is that dist/@vitest/browser/context.js (generated by vite-plus's build) does not export server, but @storybook/addon-vitest does a static import of server from @vitest/browser/context:

import { server } from "@vitest/browser/context";
var { getInitialGlobals } = server.commands

Here's the chain:

1. @vitest/browser's root context.js (package root, not dist/) exports server = null as a static analysis placeholder — Vitest replaces it with a virtual module at runtime.
2. @vitest/browser's dist/context.js (the actual runtime file) exports only { cdp, createUserEvent, locators, page, utils } — no server.
3. Vite-plus's packages/test/build.ts copies @vitest/browser/dist/ → dist/@vitest/browser/ (in copyVitestPackages()), so dist/@vitest/browser/context.js is a copy of @vitest/browser/dist/context.js.
4. package.json exports map ./browser/context and ./context to ./dist/@vitest/browser/context.js.
5. When vitest is overridden to @voidzero-dev/vite-plus-test, @vitest/browser/context resolves to that file → server not found → SyntaxError.

---

Is it Fixable?

Yes — and it's a targeted fix in packages/test/build.ts.

---

Implementation Plan

The fix is to patch dist/@vitest/browser/context.js to add a browser-safe server export. The serverStub object is already defined elsewhere in build.ts (patchVitestBrowserPackage / rewriteImports) and provides exactly what's needed:

export const server = {
  get browser() { return window.__vitest_browser_runner__?.config?.browser?.name; },
  get config() { return window.__vitest_browser_runner__?.config || {}; },
  get commands() { return window.__vitest_browser_runner__?.commands || {}; },
  get provider() { return window.__vitest_browser_runner__?.provider; },
};

Specific steps:

1. In build.ts, add a new function patchBrowserContextFile() (or extend the existing patchVitestBrowserPackage) to:

   • Read dist/@vitest/browser/context.js
   • Check if it already exports server (guard for future vitest versions that add it back)
   • If not present, append the exported server stub

2. Call the patch in the build flow, after copyVitestPackages() (step 2) and rewriteVitestImports() (step 5) — e.g., as part of step 7 patchVitestBrowserPackage().

3. Update the .d.ts: dist/@vitest/browser/context.d.ts (or browser/context.d.ts) already re-exports from the bundled types, so server types should flow through from @vitest/browser/context.d.ts (which has the type). Verify that ServerContextOptions / server is typed in the exported .d.ts.

Relevant files:

• packages/test/build.ts — the build script (around lines 1440–1456 for patchVitestBrowserPackage, and lines 1931–1943 for the existing serverStub definition in rewriteImports)
• packages/test/package.json — the ./browser/context and ./context exports (lines 121–128)
• dist/@vitest/browser/context.js — generated file that needs the server export added

---

Potential Concern

The server.commands field from the stub returns window.__vitest_browser_runner__?.commands || {}. Storybook's addon calls server.commands.getInitialGlobals?.() with optional chaining, so if getInitialGlobals is not registered, it will gracefully return undefined → fallback to {}. This should be safe.