Vendored react-server-dom-webpack CJS breaks on ESM-only runtimes (Cloudflare Workers)

[remorses]

@vitejs/plugin-rsc vendors react-server-dom-webpack as raw CJS into dist/vendor/react-server-dom/. These files use require() and module.exports.

On pure ESM runtimes (Cloudflare Workers, Deno Deploy), production builds can fail with "require is not defined" or "exports is not defined" when the CJS vendor code leaks into ESM chunks.

Reproduction: https://github.com/remorses/vite-rsc-cloudflare-cjs-repro

pnpm install
pnpm reproduce

The repro is based on the official examples/starter-extra Cloudflare setup and locks @vitejs/plugin-rsc to 0.5.21. pnpm reproduce builds with the Cloudflare Vite plugin and fails because the RSC output still contains the CJS react-server-dom-webpack-server.edge.production.js bundle.

Fix in #1203.

[hi-ogawa]

Closing this as a false positive. The matched exports.renderToReadableStream is inside the bundler’s CommonJS interop wrapper, where exports is a synthetic per-module object created by the bundle runtime, not an ambient Worker/CommonJS global.

var __commonJSMin = (cb, mod) => () =>
  (mod || (cb((mod = { exports: {} }).exports, mod), cb = null), mod.exports);

So the repro only shows that a CJS-authored dependency was bundled into the final ESM Worker output. That is expected bundler semantics and does not mean the server build is CommonJS or that the Worker depends on unsupported top-level require/module/exports.

[remorses]

Sorry for the wrong reproduction

I ended up finding the source cause of the issue, this only happens when using Vite 7, I had Vite 7 installed globally and it caused this issue, Vite 8 handles it fine. It also comes from a complex module graph that's difficult to repro