Updates and changes in the Svelte ecosystem. Key topics include improvements to the migration script, fixes related to reactivity, CSS issues with has and not selectors, and enhancements to the Svelte compiler.
@sheepdog/svelte aims to simplify asynchronous code management in Svelte applications. The library introduces tasks with various modifiers like debounce, queue, drop, keep latest, and restart to handle different scenarios of asynchronous operations.
Updates on Svelte 5.0.8, including new features like spring and tween classes, media query support, and improvements to if blocks. The episode also includes a community showcase on GPU-rendered components with the svader library, demonstrating how to create interactive shaders with Svelte.
Durable objects and a library related to PartyKit and durable objects. The changelog section discusses several updates, including reducing hydration comments, fixing bugs related to bind groups, and improving the handling of props IDs in Astro.
Latest updates and features in the Svelte ecosystem, particularly around SvelteKit. The episode highlights the introduction of experimental async SSR (Server-Side Rendering), which allows for asynchronous operations directly within Svelte components, significantly improving developer experience.
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.
Vest is a powerful form validation framework inspired by the syntax and style of unit testing libraries like Mocha or Jest. It uses their declarative structure and makes it easy to write complex form validations that are also easy to read and maintain.
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.
SvelteKit gives developers the ability to do more with less. Less code, less energy, and consequently less time. More so, it gives you all the SEO benefits of single-page applications with client-side routing for almost instant navigation. Talk about the best of both worlds. With the techniques we'll discuss in this talk, you'll learn how to get the best of SvelteKit and unlock the superpowers you never knew you had
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.
In this live coding experiment, Domenik talks about SvelteKit, the use of monorepos in combination with turborepo and how you can use SvelteKit to generate your packages that can be used inside your monorepo.
This little demo shows you how to create your own Svelte component library and release it to npm.
SvelteKit helps us to accomplish that task in an easy way.