Join us for the last few Svelte Summit videos where you'll learn about i18n and preprocessors!

Svelte has been described as an “accessibility-first-framework”, yet its compiler warnings cover only a fragment of the issues at hand. In this talk, I’d like to explore how accessible Svelte really is and more importantly, have a look at what you can do to bridge the gap. Ideas include checking both automatically and manually for issues the compiler might overlook, like color contrast, keyboard accessibility and semantics.

Today we'll navigate the chilly landscape of SvelteKit adapters, akin to the snowy components on a glowing logic board. The stream will focus on building a custom adapter for WinterJS, demonstrating how to gear up your SvelteKit app for the winter of the web world. Bundle up for an insightful session on SvelteKit adaptation!

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: recent updates in Svelte - use of hooks.server.js in SvelteKit - differences between using +page.ts and +page.server.ts in SvelteKit

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.

Matthias tweeted a 20 line of code i18n library with Svelte and it went semi-viral: https://twitter.com/h_i_g_s_c_h/status/1344223132308164616

Svelte includes built-in animations that makes it easy to slide, scale, and fly elements in and out of the DOM. However, you need to be careful to not trigger motion sickness in your users. I will go over which Svelte transitions could cause accessibility issues and how to respect user motion preferences when using them.

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.

A demo on how to setup internationalization in a SvelteKit project using the lightweight library typesafe-i18n.

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.