SvelteKit: Document relative paths configuration #640
Merged
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.
I ran into a weird behavior while developing a SvelteKit frontend with Quinoa
Whenever a full reload happend an a nested route, it would give me a 404 error. But if I followed a link to that same route it worked just fine.
Then I tried it without Quinoa proxying the request, and there the full reload also worked perfectly fine.
It turns out that SvelteKit will assume that its base directory is whatever the current path's parent directory is if the request is proxied to it the way that Quiona does it.
By configuring it to not assume that it should be using relative paths by default, the problem was resolved.
Describe your changes
Document how to configure SvelteKit to use absolute paths in its routing.
Check List (Check all the applicable boxes)