routify VS sites

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

Minor correction, svelte repl is in sites repo, and it's well maintained and updated.

I found this GitHub issue that feels relevant to the Svelte REPL issue. It sounds like unpkg doesn't successfully resolve the dependency due to differences between CJS and ESM.

You'd need to bundle the svelte compiler, then feed the compiled output of your string through a worker containing a browser build of rollup to bundle all of the internal dependencies. Have a look at https://github.com/sveltejs/sites/tree/master/packages/repl if you really want to go through with this.

See: https://github.com/sveltejs/sites/issues/113

Here's one built with Svelte: https://hn.svelte.dev/

It's not exactly an apples-to-apples comparison for a number of reasons including implementation and hosting differences, but might be interesting to people anyway. The code lives here: https://github.com/sveltejs/sites/tree/master/sites/hn.svelt...

Assuming you cloned https://github.com/sveltejs/sites, then you need to cd into sites/ (https://github.com/sveltejs/sites/tree/master/sites) and then into the site you want. Afterwards just follow the instructions in the README (usually pnpm i and pnpm run dev).

I'm pretty sure it's just your extension misbehaving. Here is the like to the repo: https://github.com/sveltejs/sites/tree/master/sites/svelte.dev

Hm, it works for me (iOS). Might be worth opening an issue on the site repo with the issue you’re seeing.

the kit.svelte.dev site is also fully open source, but it uses a lot of components which handle almost everything also uses api.svelte.dev, a non-svelte site to get all the data so I don't know how helpful that is either