SvelteKit 2.62 has landed with a quiet but tidy improvement: you can now drop svelte.config.js entirely and configure everything inside your vite.config.js. It sounds like minor housekeeping, but it signals precisely where SvelteKit 3 is heading — and the update simultaneously requires Vite 8.0.12, the first Vite 8 release to bundle stable Rolldown 1.0.0.
One file fewer, one mental model fewer
Until now a SvelteKit project maintained two configuration files in parallel: svelte.config.js for Svelte and Kit options, and vite.config.js for build configuration. From 2.62 onward you can pass your entire config directly to the sveltekit() plugin in your Vite config. When that plugin-level config is present, svelte.config.js is completely ignored. The sv create scaffolder already defaults to the consolidated setup for new projects.
A preview of SvelteKit 3
The change is explicitly framed as a preview. SvelteKit 3 will make vite.config.js the only place for configuration — the separate file disappears entirely. That fits a broader movement across the JavaScript tooling world: fewer standalone config files, fewer opportunities for conflict or confusion, and a single source of truth per project. Shipping this as opt-in now and defaulting sv create to it considerably lowers the migration bump when version 3 drops.
Our take
We like tooling that tidies up after itself. Two configuration files for one project is one too many — and the earlier you adopt the consolidated pattern, the less friction you'll hit when SvelteKit 3 makes it mandatory. If you're starting a SvelteKit project today, put your config in vite.config.js from day one.
