Svelte 5 $effect.root Disposal and Microtask Boundary Invariant

--- description: Svelte 5 $effect.root Disposal and Microtask Boundary Invariant - Enforces deterministic teardown of unparented fine-grained reactive roots instantiated via $effect.root outside of standard Svelte component lifecycles. Prevents cross-request memory retention during SSR, node heap exhaustion, and zombie listener execution across asynchronous microtask boundaries in dynamic client-server execution paths. globs: src/**/*.{svelte,svelte.ts,svelte.js,ts,js} alwaysApply: true verified_by: "agentrules.org" license: "CC-BY-4.0" source: "https://agentrules.org/rules/svelte-5-effect-root-disposal-invariant" --- # Svelte 5 $effect.root Disposal and Microtask Boundary Invariant > **Severity**: CRITICAL | **Category**: frontend > **Anti-Pattern Warning**: Orphaned $effect.root Instantiations and Unbounded Asynchronous Reactive Registrations ## System Constraints You are a Principal Engineer enforcing Svelte 5 Runes Effect Root Disposal & Microtask Boundary Invariants. Mandate strict encapsulation of manual effect roots, zero side-effect execution during SSR contexts, and deterministic cleanup handlers across microtask and event-loop boundaries. ## Strict Guidelines - Engineers MUST ALWAYS capture and explicitly invoke the cleanup function returned by $effect.root() when instantiated outside of an auto-managed Svelte component context. - Engineers MUST NOT instantiate $effect or $effect.root within code paths that execute unconditionally during Server-Side Rendering (SSR), as servers retain no fine-grained reactive tree and trigger memory leaks. - Code MUST gate all manual $effect.root instances with browser execution guards (such as checking `typeof window !== 'undefined'` or SvelteKit's `browser` flag) before attachment to long-lived singleton services. - Services MUST implement explicit teardown interfaces (e.g., `destroy()`, `dispose()`, or `Symbol.dispose`) to execute root cleanups when dynamic instances are dereferenced or garbage-collected. - Components and composable stores NEVER leave pending asynchronous microtask chains uncancelled inside an $effect or $effect.root callback when the surrounding component unmounts. ## Bad vs Good Implementations ### Deterministic Lifecycle-Safe $effect.root in Fine-Grained Reactive Store #### Bad Antipattern (AI Common Hallucination) > **Why it fails**: Instantiating $effect.root without storing its returned teardown closure leaves the reactive branch permanently anchored in memory. On SSR, this causes cross-request heap accumulation. In client SPAs, re-instantiating the service causes zombie effects to persist. ```typescript import { $state, $effect } from 'svelte/runes'; // ANTI-PATTERN: Leaks reactive nodes per request on SSR and orphans memory in client singletons export class DynamicTelemetryService { private count = $state(0); constructor() { // $effect.root is missing; if called in an unparented module scope, this effect will outlive callers // or execute on the server during import/SSR instantiation $effect.root(() => { $effect(() => { console.log('Telemetry tick:', this.count); }); }); } public increment() { this.count++; } } ``` #### Production Standard (Correct) > **Standard**: Guards against server execution via runtime environment checks, captures the cleanup function returned by $effect.root(), and exposes deterministic teardown through both a standard destroy method and Symbol.dispose. ```typescript import { $state, $effect } from 'svelte/runes'; import { browser } from '$app/environment'; export class DynamicTelemetryService { private count = $state(0); private cleanupRoot: (() => void) | null = null; constructor() { // PRODUCTION FIX: Guard against SSR execution and store the root teardown function if (browser) { this.cleanupRoot = $effect.root(() => { $effect(() => { console.log('Telemetry tick:', this.count); return () => { // Inner microtask/listener cleanup }; }); }); } } public increment(): void { this.count++; } public [Symbol.dispose](): void { this.destroy(); } public destroy(): void { if (this.cleanupRoot) { this.cleanupRoot(); this.cleanupRoot = null; } } } ```

Architectural Specification & Invariant Rationale

Architectural Invariant Design: Svelte 5 $effect.root Disposal and Microtask Boundary Invariant

Svelte 5 $effect.root Disposal and Microtask Boundary Invariant defines an industrial-grade behavioral standard for frontend engineering. Enforces deterministic teardown of unparented fine-grained reactive roots instantiated via $effect.root outside of standard Svelte component lifecycles. Prevents cross-request memory retention during SSR, node heap exhaustion, and zombie listener execution across asynchronous microtask boundaries in dynamic client-server execution paths. Modern software architectures require strict adherence to deterministic patterns to guarantee high availability, maintainability, and zero security vulnerabilities.

Framework Paradigm Shift & Drift MechanicsLLMs are trained on millions of open-source repositories containing outdated code, legacy idioms, and unpatched antipatterns. When coding assistants generate implementations for this stack, they default to common statistical tokens: Orphaned $effect.root Instantiations and Unbounded Asynchronous Reactive Registrations Without an explicit system instruction file, developers spend hours debugging silent failures.

Failure Modes & Production Blast Radius

Hazard Analysis: What Breaks Without This Rule

The following failure modes have been cataloged from hundreds of hours of production code reviews where AI assistants produced non-compliant implementations:

Failure Mode	AI Symptom (The Anti-Pattern)	Severity	Production Impact & Remedy
AI Hallucination & Deprecation Drift	Orphaned $effect.root Instantiations and Unbounded Asynchronous Reactive Registrations	Critical	Violating this industrial standard introduces regression bugs, security risks, and unexpected runtime failures in production. Enforce explicit behavioral system directives across all AI coding assistants in your repository.
Silent Architecture Inconsistency	AI assistants produce mixed paradigms across files, creating fragmented codebase conventions.	Medium	Increases cognitive load during code reviews and leads to maintenance debt across engineering teams. Pin project conventions in .cursor/rules, CLAUDE.md, and AGENTS.md so all team agents follow identical guardrails.

Architectural Directives in Detail

Step-by-Step Production Directives

Each rule constraint below is injected into the AI agent's system prompt to establish deterministic boundaries:

Engineers MUST ALWAYS capture and explicitly invoke the cleanup function returned by $effect.root() when instantiated outside of an auto-managed Svelte component context.

Rationale:AI models frequently generate unconstrained code here because statistical language distributions lack project-specific architectural context. Mandating this directive ensures that generated code adheres to verified industrial production requirements.