Winners of Svelte Hack 2024 (runes-edition)!

01:24 Changelog - SvelteKit 1.27.2 02:12 Quick facts & Announcements - Normalizing events 06:02 Community Showcase - Svelte Pilot by Fenix 16:27 Discussions - Choosing a database 27:52 Q&A - How to write a preprocessor

A Svelte 5 changelog overview covering snippets, bug fixes, and migration guidance. Live coding of runes-based dynamic filtering plus exploration of effect, onMount, and reactivity features.

Routify 3 preview and walkthrough — app creation via CLI, plugin usage (Index By Name), Pico CSS integration, page ordering, and route metadata concepts. Build-time metadata generation, API data fetching (e.g., GitHub), Markdown-to-HTML conversion, dynamic routes and imports for SSR, navigation and multi-router features, and router state persistence.

If you are building a Single-Page App (SPA), you will likely need a router for your app. With the lack of an official router for Svelte 3, there's quite a few options, so which one should you pick? In this talk, we'll look at the two different kinds of routers (based on the History API or based on the page's hash), how they differ, and when you should pick which. We'll also go through a demo of implementing routing for a Svelte 3 SPA using svelte-spa-router.

Routify offers a great developer experience to build the routes for your Svelte app.

Join GHOST for our Second Svelte Sirens event as she shows you the magic of Routify in Svelte Kit. Take a look at the links below to find out more about Routify, Svelte Kit, Svelte Sirens, and GHOST!

Curious about Runes? Want to get your questions answered? Here what the team has been up to?

00:00 Introduction 00:30 Announcements - Svelte Summit 01:10 Runes Primer 13:17 Runes FAQ 19:20 Rune helpers and stores with Hunter 26:26 Runify demo and fine-grained reactivity with Paolo 35:00 The library maintainer’s perspective with Hunter 45:08 Poll: the kinds of applications we make 53:25 Paul proposes Runes be a compiler-based toolchain separated from Svelte, similar to RxJS 1:01:11 Everyone’s impressions of Runes 1:02:48 Tantei-Kun likes the $props Rune 1:07:32 Poll: everyone’s impression of Runes so far

When people hear metaframework, the first thing they think of is usually SSR. However, SvelteKit also supports other rendering strategies like CSR and prerender. As the recommended way to build any Svelte app, is it going to offer the best DX for all its use cases? In this talk I'll share my experience and tell you what's good, what's bad, and what's awesome about building SPAs with Sveltekit.

In this talk we take a look at all of the Svelte 5 runes and how they compare to the reactivity model.

Simple Svelte Router for Single Page Applications (SPA).

Svelte Router adds routing to your Svelte apps. It's designed for Single Page Applications (SPA). Includes localisation, guards and nested layouts.

Svelte router using a store and components.

An exploration of client and server rendering strategies in web development, covering historical paradigms like MPA and SSG and modern approaches such as SSR and CSR. A detailed look at SvelteKit's hybrid rendering capabilities, including server-side rendering, client-side rendering, and prerendering, with guidance for applying each approach to different parts of a project.