Repository navigation
Add SvelteKit 3 support - #204
Merged
Merged
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
|
Review the following changes in direct dependencies. Learn more about Socket for GitHub.
|
Member
Author
|
@teemingc If you want to have a look, here is the equivalent on web-analytics |
Rich-Harris
reviewed
Jul 6, 2026
Rich-Harris
approved these changes
Jul 6, 2026
Rich-Harris
left a comment
Rich-Harris
left a comment
There was a problem hiding this comment.
one small question but otherwise LGTM!
andriytyurnikov
added a commit
to andriytyurnikov/andriytyurnikov.me
that referenced
this pull request
Oct 2, 2026
Migrated with `sv migrate sveltekit-3`, keeping only its semantic edits (its printer also rewrote markup: `/>` to `></path>`, entities, inline whitespace): - svelte.config.js is gone; its options now go to the sveltekit() plugin in vite.config.js - $lib is now #lib via package.json `imports`, $app/environment is $app/env, and jsconfig.json extends $app/tsconfig - resolve() takes paths without a leading slash; the homepage photo, a static file, uses asset() instead - onNavigate handlers skip shallow navigations, which now fire them @vercel/analytics and @vercel/speed-insights are pinned to the canaries 2.1.0-canary.5 and 2.1.0-canary and imported from /sveltekit-next (vercel/analytics#204, vercel/speed-insights#120). Their /sveltekit entry still imports $app/stores, which Kit 3 removed, so the root layout threw and the app never hydrated. Move to stable releases once they ship. Verified: prettier, eslint, svelte-check (0 errors), 28 unit tests, 10 e2e tests, production build, and in a production preview: no page errors, client-side navigation, and pageviews queued with the right route.
Open
This branch was successfully deployed
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
2 participants
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.
🖖🏻 What's in there?
Adds SvelteKit 3 support via
@vercel/analytics/sveltekit-nextwhile keeping@vercel/analytics/sveltekiton the existing SvelteKit 2 integration.Introduces a new test application for
sveltekit@3, while preserving the previous SvelteKit app assveltekit-oldfor SvelteKit 2 coverage.🤺 How to test?
Ultimate test is to use the test apps:
Visit these apps with your devtools open on the network tab.
Click on the link to navigate away.
Check the payload of the POST to
/insights/view: you'll see the pageview attributed to the correct route.I also ran:
pnpm -F @vercel/analytics testpnpm -F @vercel/analytics buildpnpm -F sveltekit checkpnpm -F sveltekit buildpnpm -F sveltekit-old checkpnpm -F sveltekit-old build🔬 Notes to reviewers
This mirrors the SvelteKit 3 split from vercel/speed-insights#120: use
$app/statein a newsveltekit-nextexport while preserving the stable SvelteKit 2 export based on$app/stores.