Add SvelteKit 3 support - #120
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. |
teemingc
reviewed
Jul 2, 2026
teemingc
reviewed
Jul 2, 2026
dummdidumm
reviewed
Jul 2, 2026
teemingc
reviewed
Jul 2, 2026
10 tasks
dummdidumm
approved these changes
Jul 3, 2026
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
3 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/speed-insights/sveltekit-nextwhile keeping@vercel/speed-insights/sveltekiton the existing SvelteKit 2 integration, and bumps the canary package version to2.1.0-canary.Introduce a new test application deployed on Vercel for sveltekit@3
🤺 How to test?
Ultimate test is to use the test apps:
Visit these apps with your devtools open on the network tab,
Click in the body for triggering FID measurement (it's optional, in this case only LCP, TTFB and FCP will be measured)
Click on the link to navigate away
Check the payload of the POST to
/vitals: you'll see the metrics, attributed to the correct route.🔬 Notes to reviewers
Builds on and refines the excellent original attempt in #118. That PR did the important groundwork of identifying the SvelteKit 3 shift from
$app/storesto$app/state; this keeps that direction while preserving the stable SvelteKit 2 export.