Repository navigation
chore: migrate to SvelteKit 3 - #86
Merged
Merged
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
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
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.
Onyx used SvelteKit 2 and legacy imports, history state, and service-worker APIs. Upgrade to SvelteKit 3 while preserving browser back/forward navigation and offline editing.
Update SvelteKit to 3.0.0, the Vercel adapter to 7.0.0, and the Svelte compiler and plugin to their latest stable releases. Migrate imports to
#lib, declare optional private authentication variables, and use the new application and service-worker TypeScript configs. Read note history throughpage.stateand register the service worker as a module using$app/manifest. Ignore CORSOriginvariation when retrieving cached static assets so offline hydration works.Retain TypeScript 6.0.3 as approved: SvelteKit 3 requires its compiler API, which TypeScript 7 removed. The package manager added version-specific release-age exceptions for the newly released SvelteKit and Vercel adapter packages.
Validation:
vp install --frozen-lockfilevp checkvp run check, including service-worker type checkingvp test: 191 passed, 1 existing skipvp run test:e2e: 63 passed, including its production buildThree existing Svelte warnings remain. Better Auth still declares a SvelteKit 2 peer range; its session endpoint and the GitHub backup/restore browser tests pass with SvelteKit 3.