feat: sort critical tags and sort opt-in renderPriority
#89
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Problem
There are two problems which overlap:
<base>
Must be rendered before any tags with href=".."<meta charset...>
To avoid encoding issues it should come before any text which may not match the default encoding<meta http-equiv="content-security-policy">
Needs to come before any scriptsSolution
Sorting the tags is fairly straightforward, for SSR. Which is what the below PR supports.
Things get a bit complicated for client rendering due to how the DOM patching is working. Without re-working the existing patching logic it's not possible to order the tags between Vue node instances. Sorting within the node instance is possible but not as useful to the end user.
Even though non-SSR does not work, the feature is still useful, ordering meta tags is mostly an SEO optimisation in which most people would be using some SSR hybrid rendering strategy for.