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.
Ideas for v3, as I'll forget them otherwise. Certainly not set in stone if anyone has concerns or other ideas. Feedback welcome and appreciated!
./prerender
/prerender
, and only offer the prerender script through it to avoid some headaches with the RTS optional peer dep (see fix: RTS peer dep w/ Vite #13)hydrate()
exportsrender()
andhydrate()
internally and only functions correctly if used w/ iso'sprerender()
.useRoute
anduseLocation
useLocation
anduseRoute
have some overlapping properties and can end up firing between renders, leading to tearing. Consolidating down is ideal IMO.useRoute().params
->pathParams
&useRoute().query
->searchParams
vue-router
in our naming but personally I dislike the ambiguity (params
can easily refer to both path parameters & query parameters) and a few people I've spoken to seem to agree. These seem to be better & immediately understandable to anyone, regardless of which routers they've used in the past.To Do:
useLocation().url
anduseLocation().path
will just about always matchTo Think About: