svelte-starter-kit VS next-starter-kit

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

Or, Svelte Kit 2x :-) I found myself overthinking on the name part, so went ahead with the simple "Svelte Starter Kit". Call it Svelte Pack, or Svelte Starter Kit, it's going to be fundamentally about Svelte only. I think(now) that Svelte Kit Starter would have communicated the intent better but then I wouldn't have been able to keep it inline with Next Starter Kit which started it all (but currently a bit behind :-))