routify VS svelte-starter-kit

Been using Routify in all my projects since I started with Svelte like 3-4 years ago.

Anyway, it seems you have a problem with Sveltekit routing. You can still use Svelte with other SSR frameworks, such as Astro, a router like https://routify.dev, or switch to another framework altogether.

Routify is still active and new version in the works. Version 3 can be used https://github.com/roxiness/routify/tree/next

I would have to say Svelte with a router like https://routify.dev . My recent blog post originally used sveltekit but I swapped it out last minute

Consider https://github.com/roxiness/routify

Regarding some suggestions on here recommending SvelteKit: Learning SvelteKit might be a big ask depending on what you're trying to do. If you just want to stick with svelte only for now, and you want to add SPA routing capabilities, consider checking out https://routify.dev there's a ton of documentation for it and it's fairly simple to pick up. ✌🏼

Routing: We have a few third party ones such as routify, svelte-spa-router and svelte-routing as well as the clientside routers included in SvelteKit and Sapper.

if Next.js/Nuxt like needs are not something you're looking for yet, you can definitely go ahead with Svelte's default client-side app approach, with svelte-spa-router or routify for SPAs.

We chose Routify for client-side routing because this was around the time that Sapper seemed like it was being sunset in favor of Sveltekit which doesn't seem production-ready quite yet. We also have plans to statically pre-render the app so it can more-or-less work entirely offline and Routify makes that relatively straightforward (but see below).

Since svelte does a lot of compile time stuff, I would like to mention Routify, which is compile time SPA routing. For me it worked awesome to accomplish projects with many routes and the need for hash based routing.

See https://routify.dev/ and https://routify.dev/guide/installation/install-to-existing-p...

I started adding Typescript to my project. I found Svelte-Starter-Kit is useful.

You can check how it's done in Svelte Starter Kit

I love Supabase, and maintain a SvelteKit + Supabase Open-Source Starter Kit, but between Supabase and Headless CMS, for this use case, I'd definitely recommend a Headless CMS. Any headless CMS(including WordPress) you prefer.

If you want to use the load function on the server, you'd be required to maintain the JWT token in a cookie, access it on the server in an API route/endpoint, and then you'll have to make calls to those API endpoints in the load function to check a user's credentials. Something like Svelte Starter Kit's Profile Page.

It's fixed now https://github.com/one-aalam/svelte-starter-kit/issues/17

Head over to https://github.com/one-aalam/svelte-starter-kit/tree/auth-supabase to explore! (More exciting updates on the way)

Hey, you can see how it's done here