fix(vite): only consider CSS inlined when styles are actually emitted

[danielroe]

🔗 Linked issue

📚 Description

follow-up to #34950

the dedupe added there populated inlinedCSSModuleIds during the server transform for any module whose CSS imports could be resolved - including modules whose styles never actually reach the SSR response (e.g. ambient CSS imports in .ts files like FunctionalComponent.ts).

their chunk's bundled CSS link was then wrongly dropped.

(this seems to have surfaced due to a rolldown/vite change as this originally passed in CI)

[bolt-new-by-stackblitz]

Run & review this pull request in StackBlitz Codeflow.

[pkg-pr-new]

Open in StackBlitz

@nuxt/kit

npm i https://pkg.pr.new/@nuxt/kit@35006

@nuxt/nitro-server

npm i https://pkg.pr.new/@nuxt/nitro-server@35006

nuxt

npm i https://pkg.pr.new/nuxt@35006

@nuxt/rspack-builder

npm i https://pkg.pr.new/@nuxt/rspack-builder@35006

@nuxt/schema

npm i https://pkg.pr.new/@nuxt/schema@35006

@nuxt/vite-builder

npm i https://pkg.pr.new/@nuxt/vite-builder@35006

@nuxt/webpack-builder

npm i https://pkg.pr.new/@nuxt/webpack-builder@35006

commit: 3df59ba

[codspeed-hq]

Merging this PR will not alter performance

✅ 20 untouched benchmarks
⏩ 3 skipped benchmarks¹

---

_{Comparing fix/inline-styles-4.x (3df59ba) with 4.x (cd404a1)}

Footnotes

1. 3 benchmarks were skipped, so the baseline results were used instead. If they were deleted from the codebase, click here and archive them to remove them from the performance reports. ↩