Svelte 5 Runes: Explicit Cleanup Boundaries for Dynamic $effect.root Outside Component Tree

--- description: Svelte 5 Runes: Explicit Cleanup Boundaries for Dynamic $effect.root Outside Component Tree - Enforces strict explicit cleanup boundaries and deterministic disposal contracts on dynamic $effect.root instances created outside standard component trees. Prevents signal dependency retention, orphaned subscriptions, and catastrophic heap exhaustion in long-lived SSR instances and detached stateful singletons. globs: src/**/*.{ts,js,svelte,svelte.ts,svelte.js} alwaysApply: true verified_by: "agentrules.org" license: "CC-BY-4.0" source: "https://agentrules.org/rules/svelte-5-runes-effect-root-memory-barrier" --- # Svelte 5 Runes: Explicit Cleanup Boundaries for Dynamic $effect.root Outside Component Tree > **Severity**: CRITICAL | **Category**: frontend > **Anti-Pattern Warning**: Orphaned $effect.root allocations in shared modules and SSR contexts without lifecycle-bound teardown handlers. ## System Constraints You are a Principal Software Architect enforcing rigorous memory safety rules for Svelte 5 Runes. You must prevent memory leaks caused by fine-grained signals and dynamic effect roots operating outside standard component trees. Require explicit lifecycle bindings, non-SSR execution guards, and deterministic teardown contracts on every $effect.root invocation. ## Strict Guidelines - Engineers MUST ALWAYS capture and explicitly invoke the teardown function returned by `$effect.root()`. - Engineers MUST NOT instantiate `$effect.root` or long-lived signal watchers in global module scope during SSR request handling. - Custom state classes or services utilizing `$effect.root` MUST implement explicit disposal contracts (e.g., `destroy()` or `[Symbol.dispose]()`). - Dynamic root effects instantiated on behalf of a component MUST be tied to the component lifecycle via Svelte's `onDestroy` or rune cleanup hooks. - Engineers MUST guard client-only dynamic effects using environment checks (`browser` from `$app/environment`) to prevent leaking reactive graphs in Node.js/Bun SSR runtimes. - Services MUST clear internal signal subscriber references upon disposal to break strong reference cycles between closure scopes and reactive nodes. ## Bad vs Good Implementations ### Detached Reactive Store with Explicit Lifecycle Disposal #### Bad Antipattern (AI Common Hallucination) > **Why it fails**: Discarding the cleanup function returned by `$effect.root` causes signal dependencies to remain registered in Svelte's reactive graph. In SSR or recurring instantiations, every instance remains retained in memory indefinitely. ```typescript import { $state } from 'svelte/reactivity'; // ANTI-PATTERN: Creates an unbounded effect root in module/service scope with no teardown. // In SSR or dynamic service instantiation, this permanently leaks signal graphs. export class QuerySyncService { data = $state<string>(''); constructor(private url: string) { // Leaked root: cleanup function is discarded, signal listeners permanently attached $effect.root(() => { $effect(() => { fetch(this.url).then(res => res.text()).then(text => { this.data = text; }); }); }); } } ``` #### Production Standard (Correct) > **Standard**: The cleanup closure from `$effect.root` is captured and encapsulated within a deterministic `destroy` / `[Symbol.dispose]` contract. SSR guards prevent instantiation on the server, and `onDestroy` binds the service cleanup to component lifecycles. ```typescript import { browser } from '$app/environment'; import { onDestroy } from 'svelte'; // PRODUCTION INVARIANT: Teardown function captured and bound to deterministic disposal. export class QuerySyncService implements Disposable { data = $state<string>(''); private readonly cleanup: () => void; constructor(private url: string) { if (!browser) { this.cleanup = () => {}; return; } this.cleanup = $effect.root(() => { $effect(() => { const controller = new AbortController(); fetch(this.url, { signal: controller.signal }) .then(res => res.text()) .then(text => { this.data = text; }) .catch(() => {}); return () => controller.abort(); }); }); } [Symbol.dispose](): void { this.destroy(); } destroy(): void { this.cleanup(); } } // Usage helper inside components ensuring deterministic unmount cleanup export function useQuerySync(url: string): QuerySyncService { const service = new QuerySyncService(url); onDestroy(() => service.destroy()); return service; } ```

Architectural Specification & Invariant Rationale

Architectural Invariant Design: Svelte 5 Runes: Explicit Cleanup Boundaries for Dynamic $effect.root Outside Component Tree

Svelte 5 Runes: Explicit Cleanup Boundaries for Dynamic $effect.root Outside Component Tree defines an industrial-grade behavioral standard for frontend engineering. Enforces strict explicit cleanup boundaries and deterministic disposal contracts on dynamic $effect.root instances created outside standard component trees. Prevents signal dependency retention, orphaned subscriptions, and catastrophic heap exhaustion in long-lived SSR instances and detached stateful singletons. 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 allocations in shared modules and SSR contexts without lifecycle-bound teardown handlers. 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 allocations in shared modules and SSR contexts without lifecycle-bound teardown handlers.	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 teardown function returned by `$effect.root()`.

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.