Please try this experimental feature. This should bring a big performance improvement, especially for large projects that use Svelte with TypeScript.
If there are no major issues, we plan to make this the default in the next major version.
New video explaining SvelteKit remote functions and working with real-time data using live queries 🔥
youtu.be/j9fh4WC0zHo
Svelte knows about Typescript natively (you can even use it in the template! Not possible back then), CSS became more powerful and Tailwind appeared, making less/scss/typescript preprocessors not needed anymore.
And many preprocessors are better served as Vite plugins anyways.
We are finally releasing the Agentic Engineering with Svelte series! Please take a look and let me know what you think! 🧡
Svelte is among the best-stewarded projects I've experienced, as a very-online open source tech observer over 15+ years
The always-improving design is a treat. Async integration and remote functions are elegant, and recently {let/const, vite.config.ts eating svelte.config.js, and much nicer env. !!
So we rethought our assumptions and realized we don't need the config file anymore.
We can use Vite's resolveConfig method to do the heavy lifting of transforming a file path into a vite config object, then check if our plugin is in there to get the options from it.
Some background: svelte.config.js was originally created so the VS Code extension knows about the compiler options and - more crucially - the preprocessors.
They were very common back then because you e.g. had to use one to get Typescript support in Svelte. Nowadays