Svelte 5 Polymorphic Snippet Lifecycle and Closure Retain Cycle Prevention

--- description: Svelte 5 Polymorphic Snippet Lifecycle and Closure Retain Cycle Prevention - Mandates deterministic lifecycle management and closure scoping for polymorphic Svelte 5 snippets passed across reactive boundaries. Prevents detached DOM subtree retention and memory leaks caused by capturing lexical state in long-lived contexts during dynamic component unmounting. globs: src/**/*.svelte, src/**/*.svelte.ts, src/**/*.svelte.js, src/**/*.ts alwaysApply: true verified_by: "agentrules.org" license: "CC-BY-4.0" source: "https://agentrules.org/rules/svelte-5-snippet-context-leak-guardrail" --- # Svelte 5 Polymorphic Snippet Lifecycle and Closure Retain Cycle Prevention > **Severity**: CRITICAL | **Category**: frontend > **Anti-Pattern Warning**: Retaining Detached Snippet Closures and Lexical State in Long-Lived Contexts ## System Constraints You are a Principal Software Architect enforcing Svelte 5 memory safety and reactivity standards. You must prevent memory leaks caused by closure retain cycles and detached DOM subtrees in nested polymorphic snippets. Enforce strict lifecycle cleanup, prevent snippet leakage into module-level stores, and ensure all dynamic snippet registrations provide atomic teardowns. ## Strict Guidelines - Engineers MUST ALWAYS isolate snippet scope and avoid storing `Snippet` references in global context or module-scoped state without deterministic teardowns. - Engineers MUST NOT capture local reactive rune references (`$state`) inside snippets that are passed to long-lived parent registries without explicit dereferencing on unmount. - Components NEVER store polymorphic snippet delegates across conditional rendering boundaries (`{#if}`, `{#each}`) without an explicit `$effect` teardown. - Code SHOULD pass primitive identifiers or lightweight data payloads rather than raw snippet closures into multi-tenant registries or global contexts. - Services MUST ensure any subscriptions, event listeners, or observers instantiated within snippet execution contexts are terminated during the parent component unmount lifecycle. ## Bad vs Good Implementations ### Polymorphic Snippet Registration in Shared Context Registry #### Bad Antipattern (AI Common Hallucination) > **Why it fails**: Registering a snippet directly into a parent context registry without an unregister teardown retains the entire component's lexical scope and reactive nodes in memory even after the originating component is destroyed. ```typescript import { getContext } from 'svelte'; import type { Snippet } from 'svelte'; interface PortalRegistry { register: (id: string, snippet: Snippet) => void; } export function usePortalLeak(id: string, customSnippet: Snippet) { const registry = getContext<PortalRegistry>('PORTAL_KEY'); let localCounter = $state(0); // ANTI-PATTERN: Closure captures local state and snippet reference indefinitely; // unmounting the caller component never unregisters the snippet from the parent registry, // causing a detached DOM tree leak and lingering reactive dependencies. registry.register(id, customSnippet); } ``` #### Production Standard (Correct) > **Standard**: Using Svelte 5's `$effect` cleanup callback guarantees that the snippet reference and associated closure scope are cleared from the registry upon unmount, preventing detached DOM retain cycles. ```typescript import { getContext } from 'svelte'; import type { Snippet } from 'svelte'; interface PortalRegistry { register: (id: string, snippet: Snippet) => () => void; } export function usePortalSafe(id: string, customSnippet: Snippet) { const registry = getContext<PortalRegistry>('PORTAL_KEY'); // INVARIANT: Wrap registration in $effect with an explicit teardown return. // When the component unmounts or snippet dependencies change, the previous // registration is severed, releasing all closure bindings and DOM nodes. $effect(() => { const unregister = registry.register(id, customSnippet); return () => { unregister(); }; }); } ```

Architectural Specification & Invariant Rationale

Architectural Invariant Design: Svelte 5 Polymorphic Snippet Lifecycle and Closure Retain Cycle Prevention

Svelte 5 Polymorphic Snippet Lifecycle and Closure Retain Cycle Prevention defines an industrial-grade behavioral standard for frontend engineering. Mandates deterministic lifecycle management and closure scoping for polymorphic Svelte 5 snippets passed across reactive boundaries. Prevents detached DOM subtree retention and memory leaks caused by capturing lexical state in long-lived contexts during dynamic component unmounting. 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: Retaining Detached Snippet Closures and Lexical State in Long-Lived Contexts 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	Retaining Detached Snippet Closures and Lexical State in Long-Lived Contexts	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 isolate snippet scope and avoid storing `Snippet` references in global context or module-scoped state without deterministic teardowns.

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.