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 impromptu hackathon output and shouldn't be merged in its current state — it's here for mostly illustrative purposes.
For apps deployed to Vercel (and many other platforms) a SvelteKit app typically gets bundled into a single serverless function. For observability this is suboptimal since you can't group logs by route, only by path. We can fix this by exposing the matched route from SvelteKit (via a header like
x-sveltekit-matched-route
), and then forwarding that to the deployment platform (theoretically on Vercel via something likex-matched-route
, though this isn't currently implemented on the Vercel side.cc @tobiaslins
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
pnpm changeset
and following the prompts. Changesets that add features should beminor
and those that fix bugs should bepatch
. Please prefix changeset messages withfeat:
,fix:
, orchore:
.Edits