`[vite:manifest] entryCssReferenceIds is not iterable` with Vite v7+, manifest and tsx

[arelra]

Describe the bug

Using tsx to run a TS build script and Vite configuration to output a manifest results in the following error:

for (const [name, id] of entryCssReferenceIds) try {

[vite:manifest] entryCssReferenceIds is not iterable
    at Object.generateBundle (vite-manifest-repro/node_modules/vite/dist/node/chunks/config.js:29437:29)
    at Object.handler (vite-manifest-repro/node_modules/vite/dist/node/chunks/config.js:572:2)
    at <anonymous> (vite-manifest-repro/node_modules/rollup/dist/es/shared/node-entry.js:22981:40)
    at process.processTicksAndRejections (node:internal/process/task_queues:105:5) {
  code: 'PLUGIN_ERROR',
  plugin: 'vite:manifest',
  hook: 'generateBundle'
}

I suspect the issue is due to duplication of the module cache in CJS / ESM and different invocation paths using invalid module state.

Reproduction

https://github.com/arelra/vite-manifest-repro

Steps to reproduce

nvm use
npm i
npm run tsx-ts

System Info

System:
    OS: macOS 15.7.7
    CPU: (16) arm64 Apple M4
    Shell: 5.9 - /bin/zsh
  Binaries:
    Node: 22.22.2
    Yarn: 1.22.22
    npm: 10.9.7
    pnpm: 10.33.0
    bun: 1.3.5
    Deno: 2.5.4
  Browsers:
    Chrome: 148
    Firefox: 150
    Safari: 26
  npmPackages:
    vite: 7.3.2 => 7.3.2

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]

The repo is 404

[arelra]

The repo is 404

Sorry fixed. Please try now