install a separate router to navigate from there. So, if the real problem is the docs that gets intermingled with the sveltekit ones I think we could definitely be a better job there (and ironically AI could really help here with llm.txt). But for the rest most seem non issues. Sorry for the 🧵
I suppose my requirements for a framework are a little special. I need apps to be REALLY small and "svelte". Sveltekit is nothing like that. It comes with a "big" runtime for things like routing, dehydration and so on. That would be a crazy overhead for a small single-page app!
Sadly also without sveltekit the svelte runtime is getting bigger and bigger, so big in fact that we needed to abandon svelte all together which is soo sad.
Another big problem is the growing number of external dependencies. Every external lib increases bundle size, comes with security concerns and a license that needs to be cleared and communicated to the user. In my book 10+ npm deps is not "svelte".
If we really want to improve here, I would recommend to introduce monitoring of the bundle size in the CI and set a hard limit of e.g. 30-50kB that developers can count on also for the future! This would be a clear signal and a promise to be "#svelte" also in the future!
The runtime grew a bit since we moved from pure compile time reactivity to runtime reactivity. But it's still one of the smallest runtimes out there so I'm curious what you are switching to. Also most of the dependencies of svelte are just for the compiler and are generally under the svelte org
anyway. And again, it you think the sveltekit runtime is too big for your needs you can use svelte as is.
Build time reactivity was exactly was made svelte so special and small. Now with all this runtime it is on its way to be just one of the other frameworks and more and more people will see no reason to use it! 💔
Build time reactivity was awesome but it had a lot of problems unfortunately...most people tries runes and are flabbergasted by the extra possibilities it entail. And again, I'm curious, what you plan to switch to, as far as I know svelte is still one of the smallest and fastest out there.
I'm actually really curious if you can provide some specific numbers here. We expect to see some amount of increased bundle size for very small apps (last time I benched it was ~9kb max), but a significant and growing _decrease_ in bundle size the larger your app becomes.