[mikn]

A workspace member imported from server-side code still gets pre-bundled by the ssr (or a worker) environment's dep optimizer, so plugin transforms such as StyleX never run on it and the server render breaks at runtime.

• Change: the generated ts_dev_server config's member-sources plugin adds the member exclude list to every non-client environment through Vite's configEnvironment hook. The top-level optimizeDeps.exclude stays for the client.
• Goal: workspace members are served from source in every Vite environment, not only the client.
• Evidence: with dep discovery on in ssr and a worker environment, the SSR transform of an entry importing a member pointed at vite-cache/deps_ssr/shared.js and deps_worker/shared.js before this change. After it, both point at the member's source file.
• Risk and rollback: only non-client environments of dev servers with workspace members change; their optimizer cache rebuilds once because the exclude list feeds its hash. Revert the commit to roll back.
• Merges next: this PR alone, nothing stacked. Once a consumer pins it, its manual ssr exclude line can go.

Problem and change

Vite 8 hands the top-level optimizeDeps to the environment named client only; every other environment starts from defaults. Worker and SSR framework plugins turn on dep discovery there, and a member then resolves to a pre-bundle. The hook returns a partial config, which Vite merges by concatenating arrays, so a consumer's own exclude list for that environment still applies. oj's server-environment pre-optimizer resolves the config through Vite itself, so it reads the same list.

A member that a plugin names in an environment's optimizeDeps.include is still pre-bundled there: Vite does not filter includes by exclude.

Tests

• server_environment_optimizer_cannot_pre_bundle_a_workspace_member (behaviour test, Vite launcher): with discovery on in ssr and a worker environment, each environment's transform must import the member from source. It fails without the hook.

🤖 Generated with Claude Code