Using JavaScript API of "build" and "createServer" at the same time will cause HMR error.

[qq326943819]

Describe the bug

When I run the local server with "build" and "createServer" at the same time, the page can't perform HMR.

Reproduction

https://stackblitz.com/edit/node-nuu1gt?file=build%2Fdev-runner.js,src%2FApp.vue

System Info

OS: Windows 10 10.0.19043
    CPU: (16) x64 AMD Ryzen 7 5800H with Radeon Graphics
    Memory: 5.51 GB / 15.36 GB
Binaries:
  Node: 16.15.0 - C:\Program Files\nodejs\node.EXE
  npm: 8.5.5 - C:\Program Files\nodejs\npm.CMD
Browsers:
  Edge: Spartan (44.19041.1266.0), Chromium (101.0.1210.47)
  Internet Explorer: 11.0.19041.1566
npmPackages:
  @vitejs/plugin-vue: ^2.3.3 => 2.3.3
  vite: ^2.9.9 => 2.9.9

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 https://github.com/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.

[bluwy]

This is because when building, Vite will set process.env.NODE_ENV to production which wouldn't work in dev mode and Vue HMR fails as they HMR code isn't injected correctly. A solution is to run the build in dev mode too, passing mode: 'development' to the build config.

This issue isn't really easy to solve by Vite as process.env.NODE_ENV is a shared variable used by plugins too. So if you need to run the build in production, you can spawn another process to run it.

[qq326943819]

This is because when building, Vite will set process.env.NODE_ENV to production which wouldn't work in dev mode and Vue HMR fails as they HMR code isn't injected correctly. A solution is to run the build in dev mode too, passing mode: 'development' to the build config.

This issue isn't really easy to solve by Vite as process.env.NODE_ENV is a shared variable used by plugins too. So if you need to run the build in production, you can spawn another process to run it.

Thanks,I temporarily use the mode change method.