svelte 5 vs svelte 4
via PatrickJS/awesome-cursorrules
Svelte 5 migration guide: runes, snippets, and standardized event handling.
What is svelte 5 vs svelte 4?
This rule documents the key differences between Svelte 5 and Svelte 4, focusing on the introduction of runes for explicit reactivity control, snippets for reusable markup, and the shift from Svelte-specific event directives to standard HTML event attributes. Use it when migrating from Svelte 4 or building new components in Svelte 5.
- Replace reactive declarations ($:) with explicit runes: $state() for state, $derived() for computed values, and $effect() for side effects
- Convert Svelte 4 event directives (on:click) to standard HTML event attributes (onclick)
- Handle event modifiers by manually calling methods like preventDefault() instead of using modifier syntax
- Use snippets and render tags to create reusable markup chunks within components
- Understand that runes are compiler syntax and should not be imported as regular functions
Applies to
File patterns this rule matches.
Rule definition (reference)
Source of truth, from the repository.
I'm using svelte 5 instead of svelte 4 here is an overview of the changes.
.cursorrules for Svelte 5
Overview of Changes
Svelte 5 introduces runes, a set of advanced primitives for controlling reactivity. The runes replace certain non-runes features and provide more explicit control over state and effects.
Snippets, along with render tags, help create reusable chunks of markup inside your components, reducing duplication and enhancing maintainability.
Event Handlers in Svelte 5
In Svelte 5, event handlers are treated as standard HTML properties rather than Svelte-specific directives, simplifying their use and integrating them more closely with the rest of the properties in the component.
Svelte 4 vs. Svelte 5:
Before (Svelte 4):
<script>
let count = 0;
$: double = count * 2;
$: {
if (count > 10) alert('Too high!');
}
</script>
<button on:click={() => count++}> {count} / {double}</button>
After (Svelte 5):
<script>
// Define state with runes
let count = $state(0);
// Option 1: Using $derived for computed values
let double = $derived(count * 2);
// Reactive effects using runes
$effect(() => {
if (count > 10) alert('Too high!');
});
</script>
<!-- Standard HTML event attributes instead of Svelte directives -->
<button onclick={() => count++}>
{count} / {double}
</button>
<!-- Alternatively, you can compute values inline -->
<!-- <button onclick={() => count++}>
{count} / {count * 2}
</button> -->
Key Differences:
-
Reactivity is Explicit:
- Svelte 5 uses
$state()to explicitly mark reactive variables $derived()replaces$:for computed values$effect()replaces$: {}blocks for side effects
- Svelte 5 uses
-
Event Handling is Standardized:
- Svelte 4:
on:click={handler} - Svelte 5:
onclick={handler}
- Svelte 4:
-
Runes are Compiler Syntax:
- Do not import
$state,$derived,$effect,$props,$bindable, or$inspect. - Import only regular Svelte utilities that require imports, such as
tick,untrack,mount, orunmount.
- Do not import
-
No More Event Modifiers:
- Svelte 4:
on:click|preventDefault={handler} - Svelte 5:
onclick={e => { e.preventDefault(); handler(e); }}
- Svelte 4:
This creates clearer, more maintainable components compared to Svelte 4's previous syntax by making reactivity explicit and using standardized web platform features.
Related rules
SvelteKit + RESTful API + Tailwind CSS development guide with TDD and full file-path tracking.
Expert SvelteKit, Tailwind CSS, and TypeScript development standards with best practices and code patterns.
Expert guidance for SvelteKit development with TypeScript, Svelte 5 runes, and modern state management.
Swift UIKit MVVM + RxSwift development rules for reactive iOS applications.
Senior iOS engineer perspective on SwiftUI development with Swift 6 concurrency, SOLID principles, and performance optimization.

Tailwind CSS and UI component best practices for modern web applications