-
-
Notifications
You must be signed in to change notification settings - Fork 7.6k
feat(manifest): add assets field for standalone CSS entry points
#21015
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
feat(manifest): add assets field for standalone CSS entry points
#21015
Conversation
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)
assets field for standalone CSS entry points
sapphi-red
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thank you
…nks only (vitejs#21136)") into bugfix/imported-assets-dropped-for-standalone-pure-css-entry-points
|
I tried a quick update of this branch to v8.0.0-beta.1 but couldn't get it working yet. I found the I only pushed the conflict resolution for the docs for now and converted the PR to Draft since it doesn't work on version 8. |
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)