fix: SSR with relative base #8683
Merged
Conversation
This file contains 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Description
We discussed with @danielroe, using his vote to merge this one so we can release an alpha.
During SSR with relative base, we were generating paths using
import.meta.url. Relative base should be applied only for client code. This PR disables it in SSR soruntimeandurlfrom advanced base options will be used. And if the relative base shortcut is used, the global base fallbacks to/.The API for
experimental.buildAdvancedBaseOptionsmay need to be expanded to accommodate SSR. We would discuss this in other PRs and it isn't blocking the beta.What is the purpose of this pull request?