fix(nuxt): normalize manifest css file entries

[ThomasRalee]

❓ Type of change

• 📖 Documentation (updates to the documentation or readme)
• 🐞 Bug fix (a non-breaking change that fixes an issue)
• 👌 Enhancement (improving an existing functionality like performance)
• ✨ New feature (a non-breaking change that adds functionality)
• ⚠️ Breaking change (fix or feature that would cause existing functionality to change)

📚 Description

Update mapping logic on clientManifest files to segregate .css files from .js files.

📝 Checklist

• I have linked an issue or discussion.
• I have updated the documentation accordingly.

Reproduction

• Stackblitz reproduction link, CSS is not loaded properly.
• Command to reproduce: yarn generate && yarn preview

[netlify]

✅ Deploy Preview for nuxt3-docs canceled.

Name	Link
🔨 Latest commit	d70974e
🔍 Latest deploy log	https://app.netlify.com/sites/nuxt3-docs/deploys/62de8581e38516000839aac7

[pi0]

Thanks for the PR @ThomasRalee. Would you please revert your changes to package.json and playground and provide a reproduction? the linked issue seems not relevant.

[ThomasRalee]

Hi @pi0, thanks for the fast reply!

I've reverted the changes to package.json and playground, not sure how to create a reproduction. Would you mind sharing some tips on that?

[pi0]

You can fork this sandbox to add broken usecase that this pull request tries to fix. When provided, it would be nice to also include it to basic fixture (https://github.com/nuxt/framework/tree/main/test/fixtures/basic) to avoid future regressions with it.

[ThomasRalee]

Hi @pi0,

Thanks for the tips! I've created a reproduction link here, and also added a simple test to basic fixture, ensuring that the CSS stylesheet link tag is added to HTML head tags.

[ThomasRalee]

@pi0,

I am getting errors trying to run the webpack and dev fixtures on my local to resolve this 😞 :

• test:fixtures:dev

• test:fixtures:webpack

[pi0]

I can locally test on fixture and confirm it works. Building in test environment has strange behavior currently that no scripts are injected at all! Because of that, marked your new test as todo.