routify VS SvelteKit

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/

SvelteKit v1 - Main frontend framework

I suggest trying a web framework that has TypeScript support, like SvelteKit. You'll have a transpiler instead of a compiler, but you'll have the development experience you wanted.

You could then pair that with something like Remix, Next, Sveltekit, Nuxt, etc, depending on your preferred framework for your frontend.

I made a Sveltekit Auth starter if anyone needs a starting point for an app. A demo is here. It is an open source auth starter project utilizing Lucia for authentication, Skeleton for ui elements, Prisma for database connectivity and type safety and Sveltekit for the javascript framework. I also used Zod and Superforms to handle form validation and management. It has email verification, password reset, and will send an email if the user changes their email address to re-verify it. It is released as open source under an MIT license.

I believe websockets still need to be implemented natively in SvelteKit. This issue is one year old and yet to be resolved: https://github.com/sveltejs/kit/issues/1491

So Rich recently came back to the issue of custom fetch, and came up with teleporting: https://github.com/sveltejs/kit/issues/9160

A full-stack secure and performant authentication system using rust's Actix web and JavaScript's SvelteKit.

We have explored quite a handful of the technologies we set up to learn. From extracting JSON data and session tokens from request objects in actix-web to working with forms, interactive UI elements and server-side rendering with SvelteKit. We still have some missing pieces, however. What about handling Multipart FormData in actix-web? How can we integrate the popular AWS S3 to our application to scalably manage its files (images, in this context)? These questions and many more will be addressed in this post. Apologies if it's lengthy.

An authentication system is an integral part of modern applications. It's so important that almost all modern applications have some sort of it. Because of their critical nature, such systems should be secure and should follow OWAP®'s recommendations on web security and password hashing as well as storage to prevent attacks such as Preimage and Dictionary attacks (common to SHA algorithms). To demonstrate some of the recommendations, we'll be building a robust session-based authentication system in Rust and a complementary frontend application. For this article series, we'll be using Rust's actix-web and some awesome crates for the backend service. SvelteKit will be used for the frontend. It should be noted however that what we'll be building is largely framework agnostic. As a result, you can decide to opt for axum, rocket, warp or any other rust's web framework for the backend and react, vue or any other javascript framework for the frontend. You can even use rust's yew, seed or some templating engines such as MiniJinja or tera at the frontend. It's entirely up to you. Our focus will be more on the concepts.