feat(rsc): use __VITE_ENVIRONMENT_RUNNER_IMPORT__ for import.meta.viteRsc.loadModule global

[hi-ogawa]

Description

Establishes __VITE_ENVIRONMENT_RUNNER_IMPORT__ as a convention for frameworks to integrate custom environment setups with import.meta.viteRsc.loadModule.

declare global {
  function __VITE_ENVIRONMENT_RUNNER_IMPORT__(
    environmentName: string,
    id: string,
  ): Promise<any>
}

The problem:

import.meta.viteRsc.loadModule allows importing modules across environments (e.g., RSC → SSR). By default, both environments run in the main Vite process as RunnableDevEnvironment. However, frameworks like Nitro run environments in separate workers where they can communicate internally but not from the main Vite process.

The convention:

Frameworks with custom environment setups can override this global to provide their own module import logic:

// Default (set by plugin)
globalThis.__VITE_ENVIRONMENT_RUNNER_IMPORT__ = async (env, id) => {
  return server.environments[env].runner.import(id)
}

// Custom (e.g., worker-based environments)
globalThis.__VITE_ENVIRONMENT_RUNNER_IMPORT__ = async (env, id) => {
  return myWorkerRunners[environmentname].import(id)
}

This allows import.meta.viteRsc.loadModule to work seamlessly across different runtime configurations without changes to user code.

---

• Closes feat(rsc): support non global dev runner #924 (supersedes)

[pkg-pr-new]

Open in StackBlitz

npm i https://pkg.pr.new/@vitejs/plugin-react@1037

npm i https://pkg.pr.new/@vitejs/plugin-react-oxc@1037

npm i https://pkg.pr.new/@vitejs/plugin-rsc@1037

npm i https://pkg.pr.new/@vitejs/plugin-react-swc@1037

commit: 15fa1bc