Vite not importing jsx runtime correctly in development build

[fuma-nama]

Describe the bug

A few days ago I face the #130 react error, I wanted to use development build to find the cause.
However, it throws Uncaught TypeError: jsxDevRuntime.exports.jsxDEV is not a function in the browser after build.

I found those lines in index.js

...
client.createRoot(document.getElementById("root")).render(/* @__PURE__ */ React$6.createElement(React$6.StrictMode, {
  __self: globalThis,
  __source: {
    fileName: _jsxFileName,
    lineNumber: 9,
    columnNumber: 3
  }
}, /* @__PURE__ */ React$6.createElement(App, {
  __self: globalThis,
  __source: {
    fileName: _jsxFileName,
    lineNumber: 10,
    columnNumber: 5
  }
})));

It seems that the dev runtime is not correctly imported

Reproduction

https://github.com/SonMooSans/money-blog

System Info

System:
    OS: Windows 10 10.0.22000
    CPU: (12) x64 AMD Ryzen 5 3600 6-Core Processor
    Memory: 5.39 GB / 15.94 GB
  Binaries:
    Node: 16.6.2 - D:\app file\nodejs\node.EXE
    npm: 7.20.3 - D:\app file\nodejs\npm.CMD
  Browsers:
    Edge: Spartan (44.22000.120.0), Chromium (98.0.1108.62)
    Internet Explorer: 11.0.22000.120
  npmPackages:
    @vitejs/plugin-react: ^1.3.0 => 1.3.2
    vite: ^2.9.9 => 2.9.13

Used Package Manager

npm

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.

[seivan]

I recall I had the same issue and

  legacy: {
    buildRollupPluginCommonjs: true
  },

made it work.
My tsconfig is

"jsx": "preserve",
"jsxImportSource": "react",
    ```

[bluwy]

I think this is fixed in #8546 with plugin-react beta. Previously it's always forcing the prod version for dev build, causing this error.