-
-
Notifications
You must be signed in to change notification settings - Fork 6.1k
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
Manifest.json Documentation is Confusing #16525
Comments
It is recommended to output in the written order as outputting in that order is most performant for end users. But it doesn't need to be followed.
For css entrypoints, it won't have a
I think yes. But we don't have any internal checks that it doesn't contain a cycle.
No. You can pass assets as an entry point. HTML itself can be an entry point as well. |
Documentation is
Explain in Detail
On the Backend Integration page, parts 3 and 4 deal with the manifest.json file.
However, there are several parts that are not clearly explained, and I would appreciate clarification on, and may be helpful to others implementing something to convert it to HTML.
For example, asset chunks are not entry or dynamic entry chunks, but do not have a key starting with
_
.Questions relating to Section 4:
css
section, or does that include iffile
is a css file as well?file
, what is the impact of loading the files after loading all thecss
sections?Edit:
Your Suggestion for Changes
Consider breaking manifest.json documentation to its own file.
Section 3
Section 4
*Add information to the 2nd bullet point to answer the questions above.
Reproduction
https://vitejs.dev/guide/backend-integration.html
Steps to reproduce
No response
The text was updated successfully, but these errors were encountered: