Svelte 5 Universal Runes Memory Scoping and Root Effect Teardown

--- description: Svelte 5 Universal Runes Memory Scoping and Root Effect Teardown - Enforces strict memory boundary management and explicit root effect disposal for Svelte 5 universal runes instantiated outside component lifecycles. Guarantees that reactive closures in long-lived client contexts, service modules, and micro-frontend hosts do not retain detached DOM nodes or leak heap across view transitions. globs: src/**/*.{svelte,svelte.ts,ts,js} alwaysApply: true verified_by: "agentrules.org" license: "CC-BY-4.0" source: "https://agentrules.org/rules/svelte-5-runes-memory-scoping-root-effect-teardown" --- # Svelte 5 Universal Runes Memory Scoping and Root Effect Teardown > **Severity**: CRITICAL | **Category**: frontend > **Anti-Pattern Warning**: Unmanaged $effect.root Instantiations and Leaked Universal Reactive Closures Across View Transitions ## System Constraints You are a Principal Software Architect enforcing deterministic reactive lifecycles in Svelte 5 applications. Your objective is to eliminate memory leaks resulting from universal runes ($state, $derived, $effect) initialized in non-component modules (.svelte.ts) and external micro-frontend boundaries. Mandate strict encapsulation of $effect.root scopes, enforce explicit cleanup binding to view/boundary lifecycles, and reject naked reactive closures and uncontained global state factories. ## Strict Guidelines - Engineers MUST ALWAYS store and invoke the cleanup closure returned by `$effect.root()` whenever reactive tracking contexts are instantiated outside Svelte components (.svelte.ts classes, factory functions, or runtime mount points). - Engineers MUST NOT execute raw `$effect()` inside universal utility or state classes without an active tracking scope or an enclosing `$effect.root()` container. - Code SHOULD encapsulate shared universal reactive state within framework-managed context trees (`setContext`/`getContext`) rather than persistent global module-level singleton objects. - Services MUST expose an explicit disposal contract (`destroy()`, `dispose()`, or `[Symbol.dispose]()`) that triggers internal effect cleanup, detaches listeners, and sets state references to inert values. - Micro-frontend hosts and route transition orchestrators MUST invoke teardown callbacks before unmounting guest applications or re-initializing reactive stores to prevent retain cycles in the client memory graph. ## Bad vs Good Implementations ### Universal Reactive Service Lifecycle and Teardown Management #### Bad Antipattern (AI Common Hallucination) > **Why it fails**: The telemetry instance initializes an `$effect.root()` within its constructor but fails to capture the returned cleanup function. Because the inner `$effect` attaches a window event listener referencing `this.handleResize`, the entire class instance and its reactive graph remain pinned in the heap indefinitely after route changes, duplicating work upon each re-instantiation. ```typescript // src/services/telemetry-sync.svelte.ts // ANTI-PATTERN: Orphaned $effect.root without teardown mechanics leads to // cumulative memory leaks and runaway subscriptions on SPA view navigation. export class TelemetrySession { count = $state(0); doubled = $derived(this.count * 2); constructor() { // Spawns tracking root without capturing the disposer or exposing lifecycle hooks $effect.root(() => { $effect(() => { console.log(`Telemetry synchronized: ${this.doubled}`); // Retains global window listener tied to this instance closure permanently window.addEventListener('resize', this.handleResize); }); }); } private handleResize = () => { this.count++; }; } ``` #### Production Standard (Correct) > **Standard**: The `TelemetrySession` maintains ownership of its reactive boundary by assigning the cleanup function returned by `$effect.root()` to `this.cleanupRoot`. Exposing a standard `destroy()` method allows consumer components or micro-frontend unmount hooks to trigger absolute teardown of all reactive listeners and inner effect subscriptions. ```typescript // src/services/telemetry-sync.svelte.ts // PRODUCTION INVARIANT: Encapsulate $effect.root teardown in a disposable lifecycle pattern. export interface DisposableService { destroy(): void; } export class TelemetrySession implements DisposableService { count = $state(0); doubled = $derived(this.count * 2); private cleanupRoot: () => void; constructor() { // Invariant: Capture the root effect disposer directly upon scope creation this.cleanupRoot = $effect.root(() => { $effect(() => { console.log(`Telemetry synchronized: ${this.doubled}`); window.addEventListener('resize', this.handleResize); return () => { window.removeEventListener('resize', this.handleResize); }; }); }); } private handleResize = () => { this.count++; }; public destroy(): void { // Deterministically tears down inner effects, derived observers, and window listeners this.cleanupRoot(); } } ```

Architectural Specification & Invariant Rationale

Architectural Invariant Design: Svelte 5 Universal Runes Memory Scoping and Root Effect Teardown

Svelte 5 Universal Runes Memory Scoping and Root Effect Teardown defines an industrial-grade behavioral standard for frontend engineering. Enforces strict memory boundary management and explicit root effect disposal for Svelte 5 universal runes instantiated outside component lifecycles. Guarantees that reactive closures in long-lived client contexts, service modules, and micro-frontend hosts do not retain detached DOM nodes or leak heap across view transitions. 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: Unmanaged $effect.root Instantiations and Leaked Universal Reactive Closures Across View Transitions 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	Unmanaged $effect.root Instantiations and Leaked Universal Reactive Closures Across View Transitions	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 store and invoke the cleanup closure returned by `$effect.root()` whenever reactive tracking contexts are instantiated outside Svelte components (.svelte.ts classes, factory functions, or runtime mount points).

Engineers MUST ALWAYS store and invoke the cleanup closure returned by `$effect.root()` whenever reactive tracking contexts are instantiated outside Svelte components (.svelte.ts classes, factory functions, or runtime mount points).

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.