routify VS svelte-starter-kit

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

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...

Example for web - https://routify.dev/

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

If you need an opinionated full-stack starter kit(with auth) I've got you covered with Svelte Starter Kit. There are few things extra, which you can replace with better alternatives.

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

SvelteKit & Supabase. See if you find this of some use: Svelte Starter Kit

I maintain a Svelte Starter Kit and all I had to do between several updates is change the layout file names, simplify the hooks, and convert the config file extensions. If you're learning Svelte in 2021, you shouldn't miss learning it, as it's "the missing CLI" and the svelte team's favoured project structure, to build full-stack server rendered and static sites, with File/Folder based routing, focus on server-less with adapters, API routes, and good baked-in conventions and constructs to support common web app needs. It's a successor to Sapper which served the aforementioned needs, with exception of adapters, which is special/unique(with no officially provided parallels in Next.js/Nuxt ecosystems yet) way to make vendor-agnostic, server-less first deployment concern a seamlessly integrated part of the framework.

It's there! Just need to push these changes https://github.com/one-aalam/svelte-starter-kit/issues/15

Svelte Starter Kit