feat!: migrate adapter to SvelteKit 3 (beta) - #20
Merged
Merged
Conversation
Target SvelteKit 3 only; drop SvelteKit 2 support.
- Replace removed builder.generateManifest + "SERVER"/"MANIFEST"
substitution with builder.generateServerInstance; node/bun handler and
stream entries now import { server } from "SERVER" and call
server.init/server.respond instead of constructing the deprecated Server.
- Read paths.base from flattened builder.config.paths.base
(builder.config.kit removed).
- Replace deprecated builder.mkdirp/builder.rimraf with node:fs.
- Rework instrumentation to createInstrumentationInitializer + bundled
initializer + per-entrypoint builder.instrument.
- Bump @sveltejs/kit peer dependency to ^3.0.0.
- Update examples to SvelteKit 3: move config from svelte.config.js into the
sveltekit() Vite plugin and replace deprecated json() with Response.json().
ivanbarlog
force-pushed
the
feat/sveltekit-3-migration
branch
from
September 30, 2026 20:24
7b131f8 to
beee072
Compare
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
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.
Summary
Migrates the adapter to SvelteKit 3, targeting v3 only (drops SvelteKit 2 support). Ships as a beta for testing against expense-ease.
Changesets beta pre-mode is active (
.changeset/pre.json), so the Version Packages PR will compute a-beta.Nversion. With the pendingminor(SK3 migration) +patch(keep-active) changesets, this resolves to0.9.0-beta.0under thebetadist-tag.Adapter changes
builder.generateManifest+"SERVER"/"MANIFEST"string-substitution flow withbuilder.generateServerInstance(...). The emitted module exports a readyserverobject, so the node/bun handler & stream entries nowimport { server } from "SERVER"and callserver.init(...)/server.respond(...)instead of constructing the deprecatedServerclass.paths.basefrom the flattenedbuilder.config.paths.base(builder.config.kitwas removed).builder.mkdirp/builder.rimrafwithnode:fs.createInstrumentationInitializer(...)→ include initializer in the bundle → per-entrypointbuilder.instrument(...).@sveltejs/kitpeer dependency to^3.0.0; pin dev dep to3.0.0-next.31.Examples
svelte.config.js(unsupported in v3) into thesveltekit({...})Vite plugin; delete thesvelte.config.jsfiles.json()withResponse.json(...).Verification
bun run check(oxfmt + oxlint): 0 warnings, 0 errorsbun test: 75 pass, 0 fail (47 AWS-gated integration tests skipped)bun --bun run build.ts: succeedstsc --noEmit: passes against the real v3 typesFollow-ups before/after beta
^3.0.0does not match-nextprereleases under semver, so consumers on a v3 prerelease see a benign peer warning during install.instrumentation.server.*); validate on a real deploy if a consumer enables it.sourcemap: "linked").changeset pre exit) before cutting the stable0.9.0.