svelte-navigator VS svelte-materialify

I went to the svelte-navigator github repo and they say that they support SSR. Now, if you use only ssr and not csr, that will reload the page on every navigation.That is because in ssr your front-end asks for entire page from server and doesn't just update components in front-end. For instance here they provide an example with ssr: https://github.com/mefechoel/svelte-navigator/tree/main/example/ssr

Well, depending on your project, you could try svelte-navigator.

But yeah, at the end of the day I guess the actual problem here is that the docs are more opinionated towards Sveltekit. I guess they're focusing on Sveltekit right now so I understand why they wouldn't want to maintain a whole separate project for the router like react, vue, etc right now. But maybe making the docs less opinionated and adding more examples for other use cases would be ideal. I ended up using svelte without sveltekit + this client router for svelte + golang and we are very happy with the results.

For example, have a look at this button. It's a button for a Material design Svelte library. The styling is in a Sass (SCSS) file. The structure and any logic/script is in the .svelte file.

Svelte Materialify

Due to this popularity, devs have introduced several awesome UI component frameworks/libraries like Svelte Material UI, Smelt, Svelte Materialify and Sveltestrap.

I dont know why the https://github.com/TheComputerM/svelte-materialify decided to go on their own way instead of working with SMUI people. May be they are ahead in Typescript support?