CSS files are incorrectly excluded from assets array in manifest.json

[Rich-Harris]

Describe the bug

The manifest.json file emitted when build.manifest is true contains an object full of chunks, where some of those chunks have an assets array containing the path, relative to the output directory, of any assets referenced by that chunk.

For example if my stuff directory contains a file called text.txt, and I have a module like this...

export const stuff = import.meta.glob('./stuff/**', {
  eager: true,
  query: '?url'
});

...then the chunk that contains that module will look something like this in the manifest:

  "_stuff.js": {
    "file": "chunks/stuff.js",
    "name": "stuff",
    "assets": [
      "assets/text.txt"
    ]
  }

For whatever reason, .css files are excluded from this array — in other words if my stuff directory also contains a styles.css file, it will not be included in assets. (Nor is it included in the chunk's css array, not that it should be.)

The same thing happens if you import the asset directly:

import asset from './stuff/styles.css?url';

Reproduction

https://github.com/Rich-Harris/vite-glob-css

Steps to reproduce

npm install && npm run build, then inspect dist/.vite/manifest.json.

System Info

System:
    OS: macOS 14.4.1
    CPU: (10) arm64 Apple M1 Pro
    Memory: 268.14 MB / 32.00 GB
    Shell: 5.9 - /bin/zsh
  Binaries:
    Node: 20.14.0 - ~/Library/pnpm/node
    npm: 10.7.0 - ~/Library/pnpm/npm
    pnpm: 9.2.0 - ~/Library/pnpm/pnpm
    bun: 1.0.10 - ~/.bun/bin/bun
  Browsers:
    Chrome: 126.0.6478.57
    Chrome Canary: 124.0.6316.0
    Safari: 17.4.1
  npmPackages:
    vite: ^5.3.1 => 5.3.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.