feat: head.startElements support #28
Open
+42
−2
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Author
|
@rschristian wdyt? |
crutch12
commented
Dec 9, 2025
crutch12
force-pushed
the
feat/head-start-elements
branch
from
aace7f4 to
d6f8b61
Compare
crutch12
force-pushed
the
feat/head-start-elements
branch
from
d6f8b61 to
fadcf29
Compare
Member
|
I really dislike the API, What resources are you going to discover upon prerendering that you need to inject at the start of the head? CSS, or |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
There are cases where we need inject head elements in the start of
<head>tag (e.g.<base href="/">)Solution
Support
head.startElementsoption