svelte-it-will-scale

That N is very large. E.g. here's a page that talks about it: https://github.com/halfnelson/svelte-it-will-scale. I'll note that was done with Svelte 3 and that with Svelte 4 components are at least 10% smaller, so it's actually even better than that. SvelteKit is also very efficient at JS splitting per-route thanks to Vite. It ensures only the JS that is necessary for a page is loaded and you're extremely unlikely to be using anywhere near that many components. Based on the article above, you'd have to have three entire sites worth of components on a single page.

yes am aware, but also in any realistic scenario, code splitting comes in well before the crossover point where that even remotely comes into question. this has been independently verified twice now: https://twitter.com/sveltesociety/status/1301168598988107776... https://svelte-scaling.acmion.com/ https://github.com/halfnelson/svelte-it-will-scale sveltekit has further opportunities for whole-app optimization but honestly given this research i lost interest bc its more than good enough

- The large bundle sizes were recently addressed here. It doesn't seem to be a problem in practice: https://github.com/halfnelson/svelte-it-will-scale - You could perfectly fine write update functions á la React for your component state if that is what you prefer. Personally I don't feel that's necessary and prefer Svelte's direct way.