AgentRules.org
RulesStacksClientsAuditorPrunerSelf-HealRFCsBenchmarkCLICI/CDAuthorsSubmit
This specification is maintained by the AgentRules Working Group. Have enhancements or want to claim maintainership?Submit Specification →
frontendcritical PriorityID: vite-rolldown-federation-boundary-isolation

Vite 6 Rolldown Module Federation Chunk Boundary and Lifecycle Isolation

Enforces strict chunk boundary isolation and deterministic initialization sequencing across dynamic module federation remotes in Vite 6 with Rolldown. Prevents cyclic dependency deadlocks, shared singleton scope contamination, and cross-micro-frontend memory retention leaks through isolated async bootstrap fencing and explicit cleanup lifecycles.

Prohibited Anti-Pattern: Unfenced Synchronous Federation Imports Inducing Rolldown Module Graph Deadlocks and Leaked Shared Scopes

Export Ready-to-Drop Configuration

Select format below to copy code or download file directly.

---
description: Vite 6 Rolldown Module Federation Chunk Boundary and Lifecycle Isolation - Enforces strict chunk boundary isolation and deterministic initialization sequencing across dynamic module federation remotes in Vite 6 with Rolldown. Prevents cyclic dependency deadlocks, shared singleton scope contamination, and cross-micro-frontend memory retention leaks through isolated async bootstrap fencing and explicit cleanup lifecycles.
globs: vite.config.{ts,js,mjs}, src/**/*.{ts,tsx}, packages/**/src/**/*.{ts,tsx}
alwaysApply: true
verified_by: "agentrules.org"
license: "CC-BY-4.0"
source: "https://agentrules.org/rules/vite-rolldown-federation-boundary-isolation"
---

# Vite 6 Rolldown Module Federation Chunk Boundary and Lifecycle Isolation

> **Severity**: CRITICAL | **Category**: frontend
> **Anti-Pattern Warning**: Unfenced Synchronous Federation Imports Inducing Rolldown Module Graph Deadlocks and Leaked Shared Scopes

## System Constraints
You are a Principal Software Architect enforcing deterministic module federation fences in Vite 6 / Rolldown micro-frontend architectures. Your mission is to eradicate circular evaluation deadlocks and uncollectable memory retained across dynamic remote boundaries. You must strictly enforce async initialization fences (bootstrap decoupling), runtime container lifecycle guards, explicit teardown registrations, and strict shared scope singleton deduplication.

## Strict Guidelines
- Engineers MUST ALWAYS isolate micro-frontend entry points using an asynchronous dynamic import fence (e.g., `import('./bootstrap')`) to ensure Rolldown resolves shared module graph chunks before root-level execution.
- Engineers MUST NOT import shared dependencies synchronously inside the federation container entry point or evaluate side-effects at the top level of exposed modules.
- Code SHOULD configure explicit `shareScope` definitions and enforce singleton versions (`singleton: true`, `strictVersion: true`) in the Rolldown/Vite federation configuration to prevent duplicate runtime initializations.
- Services MUST implement explicit unmount and disposal contracts (e.g., abort controllers, event unbinding, cache clearing) when remote micro-frontend boundaries are dynamically unmounted from the DOM.
- Components NEVER store direct references to foreign remote DOM nodes or micro-frontend container registries without wrapping them in WeakRef or finalizing cleanup hooks inside unmount lifecycle events.

## Bad vs Good Implementations
### Asynchronous Entry Point Fencing and Teardown Lifecycle

#### Bad Antipattern (AI Common Hallucination)
> **Why it fails**: Synchronously importing and interacting with shared singletons at the root entry file blocks Rolldown from properly scheduling chunk initializations, creating circular evaluation deadlocks during remote negotiation. Failing to expose or handle an unmount lifecycle leaks listener subscriptions and memory when the host switches views.
```typescript
// entry.ts (Host / Remote entry point)
import { mountApp } from './mount';
import { eventBus } from '@shared/event-bus'; // Direct synchronous import of shared singleton

// Top-level side-effect execution locks Rolldown chunk evaluation
eventBus.subscribe('SESSION_EXPIRED', () => {
  console.warn('Session expired');
});

const root = document.getElementById('root')!;
mountApp(root); // Directly mounting without an unmount/cleanup fence
```

#### Production Standard (Correct)
> **Standard**: Decoupling entry through dynamic import bootstrap allows Rolldown's module graph to initialize all federated shared dependencies prior to execution. The export exposes an explicit mount/unmount contract utilizing an AbortController to cleanly eliminate lingering event listeners and foreign DOM references upon micro-frontend teardown.
```typescript
// entry.ts (Async Fence)
import('./bootstrap').catch((err) => {
  console.error('Failed to initialize micro-frontend bootstrap fence:', err);
});

// bootstrap.ts
import { mountApp } from './mount';
import { eventBus } from '@shared/event-bus';

export interface RemoteMountHandle {
  unmount: () => void;
}

export function mount(container: HTMLElement): RemoteMountHandle {
  const controller = new AbortController();
  const { signal } = controller;

  eventBus.subscribe('SESSION_EXPIRED', () => {
    console.warn('Session expired');
  }, { signal });

  const teardownDom = mountApp(container);

  return {
    unmount: () => {
      controller.abort();
      teardownDom();
    }
  };
}
```

### Deterministic Shared Scope Configuration in Vite 6 Rolldown

#### Bad Antipattern (AI Common Hallucination)
> **Why it fails**: Omitting explicit singleton controls allows different micro-frontends to bundle or instantiate multiple runtime contexts (e.g., duplicated React dispatcher instances), causing severe hook breakage, inconsistent internal state, and stale chunk memory leaks.
```typescript
// vite.config.ts
import { defineConfig } from 'vite';
import federation from '@originjs/vite-plugin-federation';

export default defineConfig({
  plugins: [
    federation({
      name: 'remote_catalog',
      filename: 'remoteEntry.js',
      exposes: {
        './Catalog': './src/Catalog.tsx'
      },
      shared: ['react', 'react-dom'] // Unpinned shared chunks allow multiple mismatched runtime instances
    })
  ]
});
```

#### Production Standard (Correct)
> **Standard**: Specifies deterministic shared module boundaries with `singleton: true` and `strictVersion: true`. This prevents duplicate runtime instances and enforces clean fallback resolution across module federation host and remote boundaries.
```typescript
// vite.config.ts
import { defineConfig } from 'vite';
import { federation } from '@module-federation/vite';

export default defineConfig({
  plugins: [
    federation({
      name: 'remote_catalog',
      filename: 'remoteEntry.js',
      exposes: {
        './Catalog': './src/Catalog.tsx'
      },
      shared: {
        react: {
          singleton: true,
          requiredVersion: '^18.3.0',
          strictVersion: true
        },
        'react-dom': {
          singleton: true,
          requiredVersion: '^18.3.0',
          strictVersion: true
        }
      }
    })
  ],
  build: {
    target: 'chrome89',
    modulePreload: false
  }
});
```
Recommended MCP Servers (mcp-serverlist.com)

Equip agent with system tools to verify code for this stack.

Vite Rolldown Module Graph Inspector
MCP endpoint for inspecting Rolldown chunk generation graphs and validating isolated federation boundaries.
Recommended Agent Skills (askills.dev)

Ready-to-use executable skill functions tailored to this stack.

Micro-Frontend Heap & Cyclic Dependency Auditor
CLI tool to detect circular dependencies across package boundaries and audit isolated build artifacts.
Architectural Specification & Invariant Rationale

Architectural Invariant Design: Vite 6 Rolldown Module Federation Chunk Boundary and Lifecycle Isolation

Vite 6 Rolldown Module Federation Chunk Boundary and Lifecycle Isolation defines an industrial-grade behavioral standard for frontend engineering. Enforces strict chunk boundary isolation and deterministic initialization sequencing across dynamic module federation remotes in Vite 6 with Rolldown. Prevents cyclic dependency deadlocks, shared singleton scope contamination, and cross-micro-frontend memory retention leaks through isolated async bootstrap fencing and explicit cleanup lifecycles. 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: Unfenced Synchronous Federation Imports Inducing Rolldown Module Graph Deadlocks and Leaked Shared Scopes 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 ModeAI Symptom (The Anti-Pattern)SeverityProduction Impact & Remedy
AI Hallucination & Deprecation DriftUnfenced Synchronous Federation Imports Inducing Rolldown Module Graph Deadlocks and Leaked Shared ScopesCritical
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 InconsistencyAI 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:

1

Engineers MUST ALWAYS isolate micro-frontend entry points using an asynchronous dynamic import fence (e.g., `import('./bootstrap')`) to ensure Rolldown resolves shared module graph chunks before root-level execution.

Engineers MUST ALWAYS isolate micro-frontend entry points using an asynchronous dynamic import fence (e.g., `import('./bootstrap')`) to ensure Rolldown resolves shared module graph chunks before root-level execution.

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.
Enforcement:Integrated into the Agent Pack rule file. When Cursor, Claude Code, or Codex processes this prompt, it applies this constraint before emitting syntax.
2

Engineers MUST NOT import shared dependencies synchronously inside the federation container entry point or evaluate side-effects at the top level of exposed modules.

Engineers MUST NOT import shared dependencies synchronously inside the federation container entry point or evaluate side-effects at the top level of exposed modules.

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.
Enforcement:Integrated into the Agent Pack rule file. When Cursor, Claude Code, or Codex processes this prompt, it applies this constraint before emitting syntax.
3

Code SHOULD configure explicit `shareScope` definitions and enforce singleton versions (`singleton

Code SHOULD configure explicit `shareScope` definitions and enforce singleton versions (`singleton: true`, `strictVersion: true`) in the Rolldown/Vite federation configuration to prevent duplicate runtime initializations.

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.
Enforcement:Integrated into the Agent Pack rule file. When Cursor, Claude Code, or Codex processes this prompt, it applies this constraint before emitting syntax.
4

Services MUST implement explicit unmount and disposal contracts (e.g., abort controllers, event unbinding, cache clearing) when remote micro-frontend boundaries are dynamically unmounted from the DOM.

Services MUST implement explicit unmount and disposal contracts (e.g., abort controllers, event unbinding, cache clearing) when remote micro-frontend boundaries are dynamically unmounted from the DOM.

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.
Enforcement:Integrated into the Agent Pack rule file. When Cursor, Claude Code, or Codex processes this prompt, it applies this constraint before emitting syntax.
5

Components NEVER store direct references to foreign remote DOM nodes or micro-frontend container registries without wrapping them in WeakRef or finalizing cleanup hooks inside unmount lifecycle events.

Components NEVER store direct references to foreign remote DOM nodes or micro-frontend container registries without wrapping them in WeakRef or finalizing cleanup hooks inside unmount lifecycle events.

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.
Enforcement:Integrated into the Agent Pack rule file. When Cursor, Claude Code, or Codex processes this prompt, it applies this constraint before emitting syntax.
Technical Questions & Answers

Frequently Asked Technical Questions

Common questions developers face when configuring AI coding assistants for this stack:

Q:Why is Vite 6 Rolldown Module Federation Chunk Boundary and Lifecycle Isolation critical for AI coding assistants?

Enforces strict chunk boundary isolation and deterministic initialization sequencing across dynamic module federation remotes in Vite 6 with Rolldown. Prevents cyclic dependency deadlocks, shared singleton scope contamination, and cross-micro-frontend memory retention leaks through isolated async bootstrap fencing and explicit cleanup lifecycles. Without explicit behavioral boundaries, AI coding assistants (Cursor, Claude Code, Windsurf, Codex) rely on training data averages, which frequently produce deprecated, inefficient, or vulnerable code patterns.

Q:How does adopting this rule prevent AI hallucinations?

This rule explicitly declares what the AI must avoid (Unfenced Synchronous Federation Imports Inducing Rolldown Module Graph Deadlocks and Leaked Shared Scopes) and prescribes verified positive examples. Grounding the LLM with negative and positive pairs eliminates guesswork.

Q:Which AI coding environments are supported?

This specification is multi-platform compatible: Cursor (.cursor/rules/*.mdc & .cursorrules), Anthropic Claude Code (CLAUDE.md), Windsurf (.windsurfrules), Codex / Cline (AGENTS.md), and GitHub Copilot (.github/copilot-instructions.md).

Q:Can I combine this rule with other technology stacks?

Yes. Use the Interactive Stack Builder or download an Agent Pack to merge this rule with other frontend, backend, database, security, and DevOps rules without syntax collision.

Open Specification · CC BY 4.0·Free for Personal, Team & Commercial In-Repo Use

Citation & Open Source Attribution Guidelines

This specification is licensed under Creative Commons Attribution 4.0 International (CC BY 4.0). You are completely free to adapt and share this rule in your workspace. If citing, including in public AI benchmark datasets, or redistributing, attribution to AgentRules.org is required.

Related FRONTEND Rules

View all rules →
frontend
119

SolidStart 1.0 Server Functions & Async Boundaries Production Standard

SolidStart 1.0 relies on the Vinxi bundler to split `server$` closures into independent HTTP POST RPC endpoints. Direct lexical closure over client signals within `server$` scopes or failure to demarcate async boundaries with `<Suspense>` causes silent serialization failures, client-bundle secret leaks, and SSR hydration mismatches. Enforcing strict parameter passing, runtime input validation, and Solid async primitives maintains security and fine-grained reactivity across network boundaries.

frontend
119

Astro 5 Actions & Content Layer Production Standard

Enforces strict type safety and architectural correctness for Astro 5 Server Actions and the zero-waterfall Content Layer API. Prevents runtime contract mismatches, hydration mismatches, and unhandled mutation exceptions across dynamic and prerendered boundaries. Failure to follow these patterns leads to silent data fetching waterfalls, build-time cache corruptions, and unhandled server action exceptions.

frontend
51

Nuxt 4 Nitro Server Engine & Shared Directory Production Standard

Nuxt 4 enforces strict boundary segregation between client UI in the app/ directory, backend endpoints in server/, and universal contracts in shared/. Violating cross-boundary isolation or maintaining module-scoped state in Nitro server handlers causes catastrophic cross-request data corruption and hydration mismatches under concurrent production traffic. Architects must enforce request-isolated H3 event contexts, universal serialization schemas, and strict path-alias boundaries.

1 Rule in Stack

Vite