I saw the July 2026 Svelte blog post announcing that SvelteKit’s configuration can now live directly inside vite.config.js. As someone who maintains several SvelteKit apps, this caught my eye because it promises a single source of truth for build tooling, reduces boilerplate, and aligns SvelteKit more tightly with the Vite ecosystem we already use daily.
Why this change matters right now
Since the first stable release of SvelteKit, the framework has relied on a separate svelte.config.js file for things like adapters, prerendering options, and preprocessors. While that separation made sense when SvelteKit was still figuring out its relationship with Vite, it also introduced a small friction point:
Two config files to keep in sync – you often end up opening both svelte.config.js and vite.config.js when tweaking SSR, environment variables, or custom Vite plugins.
Tooling confusion – IDE extensions sometimes treat the two files as unrelated, causing false warnings about unknown properties.
