routify VS SvelteKit

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

Link

Welcome to SvelteKit /> /> /> Visit href="https://kit.svelte.dev">kit.svelte.dev to read the documentation

Only, if you're going to write a fullstack app and have server rendered or statically rendered pages, you'll most likely use a meta framework like NextJs, Remix, SvelteKit, SolidStart.

I was working on a SvelteKit based local cloud project. I know that there are already solutions out there that work out of the box, but I want to try and build my own version from scratch. One of the key features is the file uploading and I had a tough time collecting all the information piece by piece. So, I hope that you find my solution helpful.

This article is all about simplifying your path to web development. We will build amazing websites with as little effort as possible with SvelteKit, a tool akin to your coding friend. We will quickly set things up, create a basic site with little coding, and easily turn it into a Progressive Web App (PWA).

SvelteKit: https://kit.svelte.dev

- The starter template is like a collection of web dev best practices.

- The community is great. Beginners should ask a lot of questions, and the Svelte community is pretty good at trying to help them.

- The DX is wonderful.

I'm building this with Kit: https://weather-sense.leftium.com

The only caveat: if your goal involves finding employment choose React (Next.js) because there are way more openings.

Everything you need to build a Svelte project, powered by create-svelte.

Svelte is a JavaScript framework that can be used to build a full-scale application or small bits of other applications. The core principle of Svelte is based on running the code at compile time; this is different from frameworks like React and Vue, which perform most of the operations in the browser while the app is running without a virtual DOM. This makes developing Svelte applications faster, bundles smaller, and performance better. Svelte is also easier to write and learn. It basically entails coding in HTML, CSS, and JavaScript with the addition of a few extensions. However, Svelte has a framework called SvelteKit which allows the implementation of more complex functionalities and features such as routing and server-side rendering. The main features of Svelte include:

Sveltekit doesn't natively support WebSockets, and even though it does support server-sent events, it does so in a clumsy way. Express supports both nicely. As a result, I used svelte-sse for server-sent events. One somewhat annoying quirk I ran into is that since svelte-sse returns a Svelte store, which my app wasn't subscribing to (the app doesn't need to read the value, just to trigger a pull as I described above), the whole thing was just optimized away by the compiler. I was initially scratching my head about why messages were not coming through. I ended up having to implement a workaround for that behavior. I don't blame the author of the library; they assumed a meaningful value would be sent to the client, which is not the case with 'poke'.