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.
Changelog and Q&A with Rich Harris. The episode covers various updates and improvements in Svelte, including support for TypeScript type assertions, fixes for scoping classes, optimizations in the compiler, and enhancements in SSR (Server-Side Rendering) and CSS pruning.
Custom stores can be used to wrap transforming data to and from storage mechanisms, either inside the browser or outside. Here we demonstrate a couple of fun transforms that have practical and real-world use.
Finite state machines provide an elegant, powerful approach for modeling complex behavior, and are ideally suited to many UI components. Alas, existing JavaScript FSM implementations feel verbose and bloated alongside Svelte's elegant, minimalist syntax. No more! svelte-fsm is the Svelte-esque FSM library. Discover the joy and benefits of using svelte-fsm to manage your components' state.
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.
The front end development landscape has been transformed since we started building Svelte and Sapper. What would a reimagined, truly modern workflow look like?
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.