Configure vite to generate relative links #94
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Right now, vite generates absolute links to assets, e.g.
/assets/foo.js. For this reason, chatterbox can only be served from the webserver root, e.g.https://example.com/, as assets are expected to be available there, i.e.https://example.com/assets/foo.js.Instead, vite can be configured to generate relative links, i.e.
assets/foo.js. In this case, the links are relative to the directory whereindex.htmlis located. This would cover both the case of serving from the webserver root and a subdirectory.This PR changes the vite config so that generated links are relative to
index.html.