In 2019, Svelte 3 turned JavaScript into a reactive language (/blog/svelte-3-rethinking-reactivity). Svelte is a web UI framework that uses a compiler to turn declarative component code like this…

App clicks: {count} clicks: {count} ...into tightly optimized JavaScript that updates the document when state like count changes. Because the compiler can 'see' where count is referenced, the generated code is highly efficient (/blog/virtual-dom-is-pure-overhead), and because we're hijacking syntax like let and = instead of using cumbersome APIs, you can write less code (/blog/write-less-code).

A common piece of feedback we get is ‘I wish I could write all my JavaScript like this’. When you’re used to things inside components magically updating, going back to boring old procedural code feels like going from colour to black-and-white.

Svelte 5 changes all that with runes, which unlock universal, fine-grained reactivity.

Introducing runes

Before we begin (#Before-we-begin)Even though we’re changing how things work under the hood, Svelte 5 should be a drop-in replacement for almost everyone. The new features are opt-in — your existing components will continue to work.

We don’t yet have a release date for Svelte 5. What we’re showing you here is a work-in-progress that is likely to change!

What are runes? (#What-are-runes) rune /ro͞on/ noun

A letter or mark used as a mystical or magic symbol.

Runes are symbols that influence the Svelte compiler. Whereas Svelte today uses let, =, the export keyword and the $: label to mean specific things, runes use function syntax to achieve the same things and more.

For example, to declare a piece of reactive state, we can use the $state rune:

App clicks: {count} clicks: {count} At first glance, this might seem like a step back — perhaps even un-Svelte-like (https://twitter.com/stolinski/status/1438173489479958536). Isn't it better if let count is reactive by default?

Well, no. The reality is that as applications grow in complexity, figuring out which values are reactive and which aren’t can get tricky. And the heuristic only works for let declarations at the top level of a component, which can cause confusion. Having code behave one way inside .svelte files and another inside .js can make it hard to refactor code, for example if you need to turn something into a store (/tutorial/svelte/introducing-stores) so that you can use it in multiple places.

Beyond components (#Beyond-components)With runes, reactivity extends beyond the boundaries of your .svelte files. Suppose we wanted to encapsulate our counter logic in a way that could be reused between components. Today, you would use a custom store (/docs/svelte/stores) in a .js or .ts file:

counterimport { function writable<T>(value?: T | undefined, start?: StartStopNotifier<T> | undefined): Writable<T>Create a Writable store that allows both updating and reading by subscription.

@paramvalue initial valuereference (/docs/svelte/svelte-store#writable)writable } from ‘svelte/store’;

export function function createCounter(): { subscribe: (this: void, run: Subscriber, invalidate?: () => void) => Unsubscriber; increment: () => void; }createCounter() { const { const subscribe: (this: void, run: Subscriber, invalidate?: () => void) => UnsubscriberSubscribe on value changes.

subscribe, const update: (this: void, updater: Updater) => voidUpdate value using callback and inform subscribers.

update } = writable(value?: number | undefined, start?: StartStopNotifier | undefined): WritableCreate a Writable store that allows both updating and reading by subscription.

@paramvalue initial valuereference (/docs/svelte/svelte-store#writable)writable(0);

return {
	subscribe: (this: void, run: Subscriber<number>, invalidate?: () => void) => Unsubscribersubscribe,
	increment: () => voidincrement: () => const update: (this: void, updater: Updater<number>) => voidUpdate value using callback and inform subscribers.

@paramupdater callbackupdate((n: numbern) => n: numbern + 1) }; }Because this implements the store contract — the returned value has a subscribe method — we can reference the store value by prefixing the store name with \(: App clicks: {count} clicks: {\)counter} clicks: {count} clicks: {$counter} This works, but it's pretty weird! We've found that the store API can get rather unwieldy when you start doing more complex things.

With runes, things get much simpler:

counter.svelte

export function function createCounter(): { readonly count: number; increment: () => number; }createCounter() {

let let count: numbercount = function $state<0>(initial: 0): 0 (+1 overload)

namespace $stateDeclares reactive state.

Example:

let count = \(state(0);@see{@link https://svelte.dev/docs/svelte/\)state (https://svelte.dev/docs/svelte/\(state) Documentation}@paraminitial The initial value\)state(0);

return {
	
	
	get count: numbercount() { return let count: numbercount },
	increment: () => numberincrement: () => let count: numbercount += 1
};

}App clicks: {\(counter} clicks: {counter.count} clicks: {\)counter} clicks: {counter.count} Outside .svelte components, runes can only be used in .svelte.js and .svelte.ts modules.

Note that we’re using a get property (https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Functions/get) in the returned object, so that counter.count always refers to the current value rather than the value at the time the function was called.

Runtime reactivity (#Runtime-reactivity)Today, Svelte uses compile-time reactivity. This means that if you have some code that uses the $: label to re-run automatically when dependencies change, those dependencies are determined when Svelte compiles your component:

const const multiplyByHeight: (width: any) => numbermultiplyByHeight = (width) => width: anywidth * height;

$: area = const multiplyByHeight: (width: any) => numbermultiplyByHeight(width);

Because the $: area = … declaration can only ‘see’ width, it won’t be recalculated when height changes. As a result, code is hard to refactor, and understanding the intricacies of when Svelte chooses to update which values can become rather tricky beyond a certain level of complexity.

Svelte 5 introduces the $derived and $effect runes, which instead determine the dependencies of their expressions when they are evaluated:

Signal boost (#Signal-boost)Like every other framework, we’ve come to the realisation that Knockout (https://knockoutjs.com/) was right all along.

Svelte 5’s reactivity is powered by signals, which are essentially what Knockout was doing in 2010 (https://dev.to/this-is-learning/the-evolution-of-signals-in-javascript-8ob). More recently, signals have been popularised by Solid (https://www.solidjs.com/) and adopted by a multitude of other frameworks.

We’re doing things a bit differently though. In Svelte 5, signals are an under-the-hood implementation detail rather than something you interact with directly. This means we don’t have the same API design constraints, and can maximise both efficiency and ergonomics. For example, we avoid the type narrowing issues that arise when values are accessed by function call, and when compiling in server-side rendering mode we can ditch the signals altogether, since on the server they’re nothing but overhead.

Signals unlock fine-grained reactivity, meaning that (for example) changes to a value inside a large list needn’t invalidate all the other members of the list. As a result, Svelte 5 is ridonkulously fast.

Simpler times ahead (#Simpler-times-ahead)Runes are an additive feature, but they make a whole bunch of existing concepts obsolete:

• the difference between let at the top level of a component and everywhere else

• export let

• $:, with all its attendant quirks

• different behaviour between