Skip to content

Conversation

@adamkoppede
Copy link
Contributor

The manifest.json file lists imported assets and CSS files per entry point, so the back end code can generate corresponding <link rel=preload> and <link rel=stylesheet>. These two manifest properties were missing for pure CSS entry points, if they weren't included by some other JavaScript entry point.

See: #18392 (comment)

The manifest.json file lists imported assets and CSS files per entry
point, so the back end code can generate corresponding
`<link rel=preload>` and `<link rel=stylesheet>`. These two manifest
properties were missing for pure CSS entry points, if they weren't
included by some other JavaScript entry point.

See: vitejs#18392 (comment)
@sapphi-red sapphi-red added p2-nice-to-have Not breaking anything but nice to have (priority) feat: build labels Oct 28, 2025
@sapphi-red sapphi-red changed the title fix(manifest): "assets" missing for standalone CSS entry points feat(manifest): add assets field for standalone CSS entry points Oct 28, 2025
Copy link
Member

@sapphi-red sapphi-red left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thank you

@sapphi-red sapphi-red added this to the 8.0 milestone Nov 20, 2025
@adamkoppede
Copy link
Contributor Author

With #21136 merged in 46d3077 ("docs: clarify manifest.json imports field is JS chunks only (#21136)"), this change also needs to update docs/guide/backend-integration.md and packages/vite/src/node/plugins/manifest.ts.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

feat: build p2-nice-to-have Not breaking anything but nice to have (priority)

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants