Optimize for Vibes: Svelte 5 and the New Age of Svelte
summary
Svelte 5 replaces compile‑time dependency tracking with runtime reactivity, introducing runes (state, derived, effect) and a signal‑based runtime so component state can live in plain JS files and be refactored without rewriting to stores. Benchmarks show faster updates, lower memory use and quicker hydration; TodoMVC measures 7.2KB in Svelte 5 vs 4.9KB in Svelte 4 and flips at ~3x size (9.8KB vs 10.1KB). Compiler is rewritten, migration supports Svelte 4 components and offers automated codemods for universal runtime reactivity with signals.
AI-written summary · about
chapters (16)
- 0:00Introduction
- 1:26Understanding Svelte
- 2:00Svelte component basics
- 7:09Why update Svelte?
- 8:14Svelte 5 runtime reactivity
- 11:23Introduction to runes
- 13:16Universal reactivity
- 14:24Using classes for state
- 15:23Runes and vibes
- 17:03Managing side effects
- 18:17Signal implementation details
- 21:14Performance improvements
- 22:18Bundle size analysis
- 23:42New features and cleanup
- 24:55Migration and adoption
- 26:02Getting started
related talks
40mSvelte, cybernetically enhanced web apps
24mSvelte: the last framework we need?
01h 14mSvelteJS Under the Hood
08mWhy Svelte is the best framework for beginner and advanced developers alike
38mLooking into the Svelte Compiler
13mWhat You Can Do For Your Framework
38mBuild your own Svelte 5
40mSvelte is Fast and Makes You Faster