[8.0.10] breaks production build

[christophe-g]

Describe the bug

This is going to be difficult to have a simple reproduction test case for, but going from 8.0.9 to 8.0.10 breaks production build for our app.

I get a Uncaught TypeError: Class extends value undefined is not a constructor or null on a fresh build: https://accessiblesurveys--preview-5h57wdjf.web.app/

Reverting back to 8.0.9 and deployed to https://accessiblesurveys.com

Vite version is the only difference between the two.

Reproduction

https://accessiblesurveys--preview-5h57wdjf.web.app/

Steps to reproduce

No response

System Info

System:
    OS: Linux 6.19 Linux Mint 22.3 (Zena)
    CPU: (16) x64 AMD Ryzen 7 7840U w/ Radeon  780M Graphics
    Memory: 16.29 GB / 30.65 GB
    Container: Yes
    Shell: 5.2.21 - /bin/bash
  Binaries:
    Node: 23.6.1 - /home/christophe/.nvm/versions/node/v23.6.1/bin/node
    Yarn: 1.22.22 - /home/christophe/.local/share/pnpm/yarn
    npm: 11.2.0 - /home/christophe/.nvm/versions/node/v23.6.1/bin/npm
    pnpm: 10.33.0 - /home/christophe/.nvm/versions/node/v23.6.1/bin/pnpm
    bun: 1.3.9 - /home/christophe/.local/share/pnpm/bun
  Browsers:
    Chrome: 147.0.7727.116
    Firefox: 150.0
    Firefox Developer Edition: 150.0
  npmPackages:
    vite: catalog: => 8.0.10

Used Package Manager

pnpm

Logs

No response

Validations

• Follow our Code of Conduct
• Read the Contributing Guidelines.
• Read the docs.
• Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
• Make sure this is a Vite issue and not a framework-specific issue. For example, if it's a Vue SFC related bug, it should likely be reported to vuejs/core instead.
• Check that this is a concrete bug. For Q&A open a GitHub Discussion or join our Discord Chat Server.
• The provided reproduction is a minimal reproducible example of the bug.

[christophe-g]

I have just redeployed a non-minified version of the faulty build - not sure that helps for debugging:

build: {
    minify: false,
}

removing rollupOptions (codeSplitting) did not help.

[jordantai]

Had the same issue. Had to revert back to v8.0.9

** UPDATE **
Adding some concrete evidence on top of the surface symptom, since we hit this too on
the 8.0.9 → 8.0.10 bump (React + @vitejs/plugin-react, automatic JSX runtime,
production build).

Issue appears to be specific to dynamic import() via React.lazy

Our error was different at the surface — Uncaught TypeError: a is not a function at
the top of a lazy-loaded chunk — but traced to the same Rollup-emitted CJS-interop
layer.

Every lazy chunk that uses react/jsx-runtime starts with:

import { ..., nf as a, ... } from "./index-XXXX.js";
var u = a();                   // throws here — "a is not a function"
// ...later...
(0, u.jsxs)(...)
(0, u.jsx)(...)

And in the main chunk:

require_jsx_runtime = __commonJSMin(((e, t) => {
  t.exports = require_react_jsx_runtime_production();
}));
// ...
export { ..., require_jsx_runtime as nf, ... };

So the failing call is require_jsx_runtime() — in 8.0.10 the __commonJSMin
wrapper is no longer returning a callable. __commonJSMin itself is imported from a
shared helper chunk:

import { ..., __commonJSMin } from "./chunk-XXXX.js";

45 lazy chunks in our build do var u = require_jsx_runtime(); u.jsx(...), so every
route that lazy-loads was broken.

Pinning vite: 8.0.9 (exact, no caret) fixed it with no other changes.

[sapphi-red]

There's a circular import in the output bundle, so I assume it's related to rolldown/rolldown#9161

icon-BLJ4A1k1.js -> index-0bgveaJ8.js -> icon-DjeyGlrZ.js -> icon-BLJ4A1k1.js

[gdnwr]

Had the same issue. Had to revert back to v8.0.9.
The development environment works normally, but errors occur after building.
The environment is too large to provide a minimal reproducible example.

[lizhen789]

编译出来的确实有问题，我查了好久，开发环境中没问题，打包后就有问题了，报的错误是isFuncation不存在