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-6-rolldown-dynamic-chunk-graph-fencing

Vite 6 Rolldown Dynamic Import Chunk Graph Fencing and Waterfall Containment

Enforces deterministic module chunk boundaries and compile-time cycle elimination in Vite 6 and Rolldown architectures. Prevents transitive chunk bleed and deep HTTP cascade preloading waterfalls across distributed enterprise micro-frontends by fencing dynamic imports behind strict architectural barriers and explicit chunk grouping strategies.

Prohibited Anti-Pattern: Unconstrained Dynamic Imports Causing Synthetic Common Chunk Splitting and Cascading Waterfall Fetches

Export Ready-to-Drop Configuration

Select format below to copy code or download file directly.

---
description: Vite 6 Rolldown Dynamic Import Chunk Graph Fencing and Waterfall Containment - Enforces deterministic module chunk boundaries and compile-time cycle elimination in Vite 6 and Rolldown architectures. Prevents transitive chunk bleed and deep HTTP cascade preloading waterfalls across distributed enterprise micro-frontends by fencing dynamic imports behind strict architectural barriers and explicit chunk grouping strategies.
globs: vite.config.{ts,js,mjs}, src/**/*.{ts,tsx,js,jsx}
alwaysApply: true
verified_by: "agentrules.org"
license: "CC-BY-4.0"
source: "https://agentrules.org/rules/vite-6-rolldown-dynamic-chunk-graph-fencing"
---

# Vite 6 Rolldown Dynamic Import Chunk Graph Fencing and Waterfall Containment

> **Severity**: CRITICAL | **Category**: frontend
> **Anti-Pattern Warning**: Unconstrained Dynamic Imports Causing Synthetic Common Chunk Splitting and Cascading Waterfall Fetches

## System Constraints
You are a Principal Software Architect enforcing deterministic Vite 6 and Rolldown chunk graph fencing. You must strictly mandate compile-time dependency fencing, eliminate cross-chunk circular dependencies, and prevent dynamic import waterfalls across micro-frontend boundaries. Reject any dynamic imports targeting internal module paths or configurations that allow Rolldown to generate unbounded synthetic shared chunks.

## Strict Guidelines
- Engineers MUST ALWAYS isolate dynamic import targets behind explicit public API facades (e.g., `features/billing/index.ts`) and NEVER dynamically import internal submodule paths (e.g., `features/billing/components/InternalModal.tsx`).
- Engineers MUST configure explicit Rolldown output chunk barriers via `build.rollupOptions.output.manualChunks` or advanced chunking strategies to eliminate unpredictable synthetic chunk proliferation.
- Engineers MUST NOT allow circular dependencies across dynamic import boundaries; cross-chunk references MUST flow in a strict, unidirectional Directed Acyclic Graph (DAG).
- Services MUST enforce strict module isolation such that dynamic micro-frontend modules only share externalized singleton dependencies defined in a hardened vendor chunk fence.
- Components NEVER trigger dynamic imports inside nested lifecycle hooks or tight iteration loops; dynamic imports MUST be hoisted to route boundaries or top-level interaction transitions wrapped in prefetch barriers.

## Bad vs Good Implementations
### Dynamic Import Fencing & Rolldown Chunk Allocation

#### Bad Antipattern (AI Common Hallucination)
> **Why it fails**: Directly importing internal submodules causes Rolldown to create dynamic transitive chunks that recursively fetch upstream shared utilities, triggering a multi-hop preload waterfall. It also risks circular chunk execution if internal components import parent utility types.
```typescript
// vite.config.ts
import { defineConfig } from 'vite';

export default defineConfig({
  build: {
    // ANTI-PATTERN: Default chunking allows Rolldown to create arbitrary common chunks
    // for shared imports between dynamic modules, triggering cascade waterfall requests
    rollupOptions: {
      output: {
        inlineDynamicImports: false
      }
    }
  }
});

// src/routes/Dashboard.tsx
// Leaking internal submodule paths across dynamic boundary
export const loadBilling = () => import('../features/billing/components/DeepInternalWidget');
```

#### Production Standard (Correct)
> **Standard**: Manual chunk fencing maps all feature code deterministically to an isolated chunk (`feature-billing`), while runtime consumers interact exclusively through a public facade. This guarantees that Rolldown produces an isolated single chunk without intermediate cascading dependencies.
```typescript
// vite.config.ts
import { defineConfig } from 'vite';

export default defineConfig({
  build: {
    target: 'esnext',
    rollupOptions: {
      output: {
        chunkFileNames: 'chunks/[name]-[hash].js',
        manualChunks(id: string) {
          // Invariant: Enforce deterministic boundary fencing per domain
          if (id.includes('/node_modules/')) {
            if (id.includes('react') || id.includes('react-dom')) {
              return 'vendor-core';
            }
            return 'vendor-deps';
          }
          if (id.includes('/src/features/billing/')) {
            return 'feature-billing';
          }
          if (id.includes('/src/features/analytics/')) {
            return 'feature-analytics';
          }
        }
      }
    }
  }
});

// src/features/billing/index.ts (Fenced Public API Facade)
export type { BillingConfig } from './types';
export { BillingWidget } from './components/DeepInternalWidget';

// src/routes/Dashboard.tsx (Isolated Dynamic Barrier)
export const loadBilling = () => import('@/features/billing').then((m) => m.BillingWidget);
```
Recommended MCP Servers (mcp-serverlist.com)

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

Dependency Cruiser MCP
Validates graph boundaries, enforces chunk fencing contracts, and detects compile-time circular module dependencies.
Recommended Agent Skills (askills.dev)

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

Rolldown Visualizer CLI
Inspects emitted dynamic chunk graphs to verify zero transitive preload waterfalls and strictly bounded chunk boundaries.
Architectural Specification & Invariant Rationale

Architectural Invariant Design: Vite 6 Rolldown Dynamic Import Chunk Graph Fencing and Waterfall Containment

Vite 6 Rolldown Dynamic Import Chunk Graph Fencing and Waterfall Containment defines an industrial-grade behavioral standard for frontend engineering. Enforces deterministic module chunk boundaries and compile-time cycle elimination in Vite 6 and Rolldown architectures. Prevents transitive chunk bleed and deep HTTP cascade preloading waterfalls across distributed enterprise micro-frontends by fencing dynamic imports behind strict architectural barriers and explicit chunk grouping strategies. 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: Unconstrained Dynamic Imports Causing Synthetic Common Chunk Splitting and Cascading Waterfall Fetches 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 DriftUnconstrained Dynamic Imports Causing Synthetic Common Chunk Splitting and Cascading Waterfall FetchesCritical
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 dynamic import targets behind explicit public API facades (e.g., `features/billing/index.ts`) and NEVER dynamically import internal submodule paths (e.g., `features/billing/components/InternalModal.tsx`).

Engineers MUST ALWAYS isolate dynamic import targets behind explicit public API facades (e.g., `features/billing/index.ts`) and NEVER dynamically import internal submodule paths (e.g., `features/billing/components/InternalModal.tsx`).

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 configure explicit Rolldown output chunk barriers via `build.rollupOptions.output.manualChunks` or advanced chunking strategies to eliminate unpredictable synthetic chunk proliferation.

Engineers MUST configure explicit Rolldown output chunk barriers via `build.rollupOptions.output.manualChunks` or advanced chunking strategies to eliminate unpredictable synthetic chunk proliferation.

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

Engineers MUST NOT allow circular dependencies across dynamic import boundaries

Engineers MUST NOT allow circular dependencies across dynamic import boundaries; cross-chunk references MUST flow in a strict, unidirectional Directed Acyclic Graph (DAG).

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 enforce strict module isolation such that dynamic micro-frontend modules only share externalized singleton dependencies defined in a hardened vendor chunk fence.

Services MUST enforce strict module isolation such that dynamic micro-frontend modules only share externalized singleton dependencies defined in a hardened vendor chunk fence.

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 trigger dynamic imports inside nested lifecycle hooks or tight iteration loops

Components NEVER trigger dynamic imports inside nested lifecycle hooks or tight iteration loops; dynamic imports MUST be hoisted to route boundaries or top-level interaction transitions wrapped in prefetch barriers.

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 Dynamic Import Chunk Graph Fencing and Waterfall Containment critical for AI coding assistants?

Enforces deterministic module chunk boundaries and compile-time cycle elimination in Vite 6 and Rolldown architectures. Prevents transitive chunk bleed and deep HTTP cascade preloading waterfalls across distributed enterprise micro-frontends by fencing dynamic imports behind strict architectural barriers and explicit chunk grouping strategies. 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 (Unconstrained Dynamic Imports Causing Synthetic Common Chunk Splitting and Cascading Waterfall Fetches) 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