What's the preffered way to make simple SPAs using Svelte now? I'm using this +layout.ts with sveltekit: > export const ssr = false; export const prerender = false; But it feels awkward for real SPAs - internal applications that have no need for server side rendering.
What's the goal of disabling SSR though? I get that hydrations value is mainly in SEO and a tiny improvement in initial draw speed, but why would you want it disabled, specifically? It's pretty much what you already wrote though. https://kit.svelte.dev/docs/single-page-apps
Svelte 5 Released
31–40 of 254 posts
Re: Svelte 5 Released
#32What's the preffered way to make simple SPAs using Svelte now? I'm using this +layout.ts with sveltekit: > export const ssr = false; export const prerender = false; But it feels awkward for real SPAs - internal applications that have no need for server side rendering.
What's the goal of disabling SSR though? I get that hydrations value is mainly in SEO and a tiny improvement in initial draw speed, but why would you want it disabled, specifically? It's pretty much what you already wrote though. https://kit.svelte.dev/docs/single-page-apps
Re: Svelte 5 Released
#33Re: Svelte 5 Released
#34Re: Svelte 5 Released
#35Earlier quoted context omitted.
What's the goal of disabling SSR though? I get that hydrations value is mainly in SEO and a tiny improvement in initial draw speed, but why would you want it disabled, specifically? It's pretty much what you already wrote though. https://kit.svelte.dev/docs/single-page-apps
Sometimes you don't want to develop a full-stack application.
You'll only need the fallback page and can omit the +layout prerender configuration. It's documented on that page
Re: Svelte 5 Released
#36I love Svelte and use it for all my personal projects and all company projects (except strictly static sites are still built with just 11ty but I hate it and want to move off it). But I'm going to wait a bit on v5 for the company, scanning all the issue headlines, it looks like there are a still a lot of unresolved edge cases: https://github.com/sveltejs/svelte/issues As for my latest personal project, upgrading righ…
Re: Svelte 5 Released
#37Do they still operate with very little backwards compatibility policy? They killed the sapper project and replaced it with sveltekit. Is sveltekit still alive?
CLI tool: https://github.com/sveltejs/cli
Edit: added the link to the CLI tool
Re: Svelte 5 Released
#38I love Svelte and use it for all my personal projects and all company projects (except strictly static sites are still built with just 11ty but I hate it and want to move off it). But I'm going to wait a bit on v5 for the company, scanning all the issue headlines, it looks like there are a still a lot of unresolved edge cases: https://github.com/sveltejs/svelte/issues As for my latest personal project, upgrading righ…
Definitely try Astro for static sites, I'm loving it!
Re: Svelte 5 Released
#39I learned Svelte 3 over a year ago and I found it very pleasant. Unlike React, Svelte is an integrated framework, no "pick your router" nonsense, I don't want to be picking a router. I like the direction Svelte going in, the old syntax was ok but not great. I wonder how this new Svelte compares with some of the other new kids on the block like solid.js and alpine.js.
nit: >React, Svelte is an integrated framework You're talking about Svelte Kit . Svelte does not have a router.