replace %svelte.assets% with relative path #3234
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.
Fixes #2697, supersedes #3088. Replaces
%svelte.assets%
insrc/app.html
with a relative path to the root (or topaths.assets
in production, if specified).In other words this...
...will work regardless of whether
paths.assets
is set, and will also work if you've setpaths.base
(or, in future, if we implement dynamic basepaths somehow) because a page like/custom-basepath/foo/bar/baz
will link to../../favicon.png
, which resolves to/custom-basepath/favicon.png
. It will still work iftrailingSlash
is"always"
.(Note that there's currently a bug around
paths.base
— static assets aren't served from there in dev mode. Needs fixing separately.)Please don't delete this checklist! Before submitting the PR, please make sure you do the following:
Tests
pnpm test
and lint the project withpnpm lint
andpnpm check
Changesets
pnpx changeset
and following the prompts. All changesets should bepatch
until SvelteKit 1.0