Vite versions after v5.0.13 are not including asset urls in build

[shivamrawal19]

Describe the bug

Initially posted on StackOverflow: https://stackoverflow.com/questions/78192074/combination-of-latest-versions-of-vite-vue-vitejs-plugin-vue-and-vite-plugin

( maybe helpful discussion: emosheeep/vite-plugin-virtual-mpa#68 )

Explanation in brief:

Vite 5.0.13 produced the correct build,
but any version above that is breaking build ( i.e. not including asset URLs in dist HTML files )

The reproduction github repo also has package.json & package-lock.json files which was working correctly. ( under folder /package-json-versions ) you can copy them to root and use them if required.

( explained different package json files below, referenced as <name>_package.json & <name>_package-lock.json )

old_but_working	old package versions	correct build	1 vulnerability in `npm audit`
old_v2_but_working	old package versions + vite 5.0.10 -> 5.0.13	correct build	no vulnerability in `npm audit`
new_but_faulty	latest package versions	faulty build	no vulnerability in `npm audit`

( My latest guess is that Vite is causing issue, but I am not sure, so do let me know if that's the case )

Reproduction

https://github.com/shivamrawal19/testmpa

Steps to reproduce

run npm install followed by npm run build

See the HTML files in the dist folder, it does not have asset URLs.

System Info

System:
    OS: Windows 11 10.0.22631
    CPU: (12) x64 12th Gen Intel(R) Core(TM) i5-12450H
    Memory: 5.63 GB / 15.63 GB
  Binaries:
    Node: 20.11.0 - C:\Program Files\nodejs\node.EXE
    npm: 10.2.4 - C:\Program Files\nodejs\npm.CMD
    pnpm: 8.6.5 - ~\AppData\Roaming\npm\pnpm.CMD
  Browsers:
    Edge: Chromium (123.0.2420.97)
    Internet Explorer: 11.0.22621.1

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.

[sapphi-red]

Duplicate of #15992