Incorrect manifest.json path for css entrypoint files (v5.0.0-beta.17)

[lubomirblazekcz]

Describe the bug

As mentioned in #11578 (comment), vite v5 includes bad path to manifest.json in case css file is entrypoint.

Reproduction

bellow

Steps to reproduce

Here is a reproduction, run npm run build

v4.5.0
https://stackblitz.com/edit/vitejs-vite-xgwzla?file=vite.config.js,dist%2Fmanifest.json

src/style.css is included correctly in manifest.json

v5.0.0-beta.17
https://stackblitz.com/edit/vitejs-vite-ma53cs?file=vite.config.js,dist%2Fmanifest.json

style.css is included incorrectly in manifest.json, path should be same as in the case with src/main.js. This was an issue that was previously fixed in v3 or v4

System Info

System:
    OS: Linux 5.0 undefined
    CPU: (8) x64 Intel(R) Core(TM) i9-9880H CPU @ 2.30GHz
    Memory: 0 Bytes / 0 Bytes
    Shell: 1.0 - /bin/jsh
  Binaries:
    Node: 18.18.0 - /usr/local/bin/node
    Yarn: 1.22.19 - /usr/local/bin/yarn
    npm: 9.4.2 - /usr/local/bin/npm
    pnpm: 8.9.2 - /usr/local/bin/pnpm
  npmPackages:
    vite: ^5.0.0-beta.17 => 5.0.0-beta.17

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.

[lubomirblazekcz]

This would definetly break a lot of backend integrations like Laravel that depends on these full entrypoint paths, such as https://laravel.com/docs/10.x/vite#configuring-vite or https://vituum.dev/config/main-options.html#input