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 weekly Svelte update from February 2024 covering changelog highlights, community showcase featuring Paraglide JS for internationalization, and discussions about Svelte 5 progress.
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.
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!
Inlang: a solution for internationalization in SvelteKit projects. The SDK and its tools simplify setup, language negotiation, and content management. This approach automates i18n processes, offering a user-friendly experience for developers and translators.
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
Paraglide-JS comes with two main innovations that make Paraglide JS the simplest, most efficient, and typesafe i18n library for SvelteKit.
1. A compiler (sounds familiar?) emits message functions instead of key-value runtime lookup logic.
2. The message functions are tree-shakable, leading to auto optimization by the bundler.
Library link: https://inlang.com/m/gerre34r/library-inlang-paraglideJs