uxr VS routify

They reference Flutter Router Package Comparative Analysis. That I found helpful too.

They are https://github.com/flutter/uxr/blob/master/nav2-usability/comparative-analysis/README.md

VRoute, AutoRoute, and Beamer were the chosen options for study which were chosen from a group of 12 because they met all the initial criteria (you can see that here). I've used Beamer so was deeply curious how this turns out.

The flutter team has done a uxr research on navigation 2.0.. you can find the repo here https://github.com/flutter/uxr/tree/master/nav2-usability

Flutter UXR team is about to conclude research for navigator 2.0 packages https://github.com/flutter/uxr/issues/31

For navigator 2/router widget we have a current user research study in progress to evaluate the gaps as well as the packages available that make it easier to use. Please let us know if you have any feedback or questions in the github project: https://github.com/flutter/uxr/tree/master/nav2-usability

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