This repository has been archived by the owner on Jan 11, 2023. It is now read-only.
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.
This is a much simpler solution to #180. Instead of specifying a
--basepath
flag, just mount the app on a path......and Sapper will figure out the rest. It will infer the basepath from the difference between
req.url
andreq.originalUrl
and assign it toreq.baseUrl
if that doesn't already exist (Express sets this value; Polka doesn't) and handle routing accordingly. It will also set a__SAPPER__.baseUrl
property so that the client-side router knows what to do.To export an app that has been mounted to a base path, you will still need to use
--basepath
:npx sapper export --basepath custom-basepath