fix(eve): move SvelteKit example config into Vite

[vercel-gh-bot-2]

The SvelteKit framework example keeps its Vercel adapter in a separate svelte.config.js, even though SvelteKit can now read this configuration from the Vite plugin. This leaves two configuration entry points for a small example.

Hypothesis

Because SvelteKit 2.63 reads inline configuration during both Vite builds and svelte-kit sync, passing the adapter directly to sveltekit() should preserve the Vercel build while removing the extra file.

This change:

• passes adapter-vercel to sveltekit() in vite.config.ts
• removes svelte.config.js
• raises the example's SvelteKit minimum to 2.63.0; version 2.62 added inline configuration, but its sync command still skipped projects without svelte.config.js

Verification

• pnpm install --frozen-lockfile
• clean-state pnpm --filter framework-sveltekit typecheck after deleting .svelte-kit
• pnpm --filter framework-sveltekit build
• pnpm exec oxlint apps/frameworks/sveltekit/vite.config.ts --deny-warnings
• pnpm exec oxfmt --check apps/frameworks/sveltekit/package.json apps/frameworks/sveltekit/vite.config.ts pnpm-lock.yaml
• pnpm check:deps
• pnpm guard:invariants
• git diff --check

Fixes #374

Requested by: colton.padden

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
eve-docs	Ready	Preview	Aug 6, 2026 7:52pm

1 Skipped Deployment

Project	Deployment	Actions	Updated (UTC)
eve-docs-4759	Skipped		Aug 6, 2026 7:52pm

[socket-security]

Review the following changes in direct dependencies. Learn more about Socket for GitHub.

Diff	Package	Supply Chain Security	Vulnerability	Quality	Maintenance	License
	npm/​@​sveltejs/​kit@​2.63.0

View full report