hash of the main chunk not changed when only modify dynamic sub component css code

[den9yon9]

Describe the bug

I changed some css code of dynamic module, then I run this build script, I found this hash of the main chunk does not change

[-Ie=Du.exports.jsx,gt=Du.exports.jsxs,Dd=lt.exports.lazy(()=>Pd(()=>import("./Home.4435181a.js"),["assets/Home.4435181a.js","assets/Home.644c3273.css"]));function-]{+Ie=Du.exports.jsx,gt=Du.exports.jsxs,Dd=lt.exports.lazy(()=>Pd(()=>import("./Home.4435181a.js"),["assets/Home.4435181a.js","assets/Home.a7afbb62.css"]));function+}

Reproduction

https://stackblitz.com/edit/vitejs-vite-wwrljy?file=main.js

System Info

System:
    OS: Linux 4.4 Ubuntu 20.04.3 LTS (Focal Fossa)
    CPU: (12) x64 Intel(R) Core(TM) i7-9750H CPU @ 2.60GHz
    Memory: 7.28 GB / 15.89 GB
    Container: Yes
    Shell: 5.0.17 - /bin/bash
 Binaries:
    Node: 14.19.3 - ~/.local/share/pnpm/node
    Yarn: 1.22.17 - ~/.local/share/pnpm/yarn
    npm: 6.14.17 - ~/.local/share/pnpm/npm
 npmPackages:
    @vitejs/plugin-react: ^2.0.0 => 2.0.0
    vite: ^3.0.0 => 3.0.4

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.

[bluwy]

Looks like this still happens in Vite 4. We need to make sure the hash of sub.js depends on sub.css too, which should make the hash change cascade.

[tessro]

We ran into this today and it caused a production issue that required an emergency rollback. It feels higher severity than p3-minor-bug, no?