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: vite6-deterministic-chunk-boundaries

Deterministic Module Graph Chunk Boundary Invariant in Vite 6

Enforces strict structural boundary isolation and deterministic content-hashing across Rollup/Rolldown chunks in Vite 6. Eliminates catastrophic cross-chunk cache-invalidation cascades across global CDN layers when incremental business-logic changes occur.

Prohibited Anti-Pattern: Monolithic vendor bundling and unconstrained manualChunks predicates causing global CDN cache bust cascades

Export Ready-to-Drop Configuration

Select format below to copy code or download file directly.

---
description: Deterministic Module Graph Chunk Boundary Invariant in Vite 6 - Enforces strict structural boundary isolation and deterministic content-hashing across Rollup/Rolldown chunks in Vite 6. Eliminates catastrophic cross-chunk cache-invalidation cascades across global CDN layers when incremental business-logic changes occur.
globs: vite.config.ts, vite.config.mts, src/**/*.{ts,tsx}
alwaysApply: true
verified_by: "agentrules.org"
license: "CC-BY-4.0"
source: "https://agentrules.org/rules/vite6-deterministic-chunk-boundaries"
---

# Deterministic Module Graph Chunk Boundary Invariant in Vite 6

> **Severity**: CRITICAL | **Category**: frontend
> **Anti-Pattern Warning**: Monolithic vendor bundling and unconstrained manualChunks predicates causing global CDN cache bust cascades

## System Constraints
You are a Principal Frontend Architect enforcing strict Vite 6 module graph chunking invariants. You must mandate deterministic manualChunks boundaries, isolate immutable vendor dependencies from mutable application entrypoints, prevent circular module chunk boundaries, and ensure assets emit stable content hashes across CI/CD builds.

## Strict Guidelines
- Engineers MUST ALWAYS isolate immutable vendor dependencies (e.g., react, react-dom, lodash-es) into discrete, explicit chunks to preserve CDN edge caching across releases.
- Engineers MUST NOT use non-deterministic manualChunks predicate functions that clump dynamic runtime dependencies into arbitrary monolithic chunks.
- Vite output configurations MUST explicitly declare immutable file patterns using `[name].[contenthash].js` or `[name].[hash].js` for entry, chunk, and asset filenames.
- Services MUST NEVER permit circular dynamic imports between isolated manual chunks, as this forces Rollup to generate synthetic bridging chunks that destabilize hashes.
- Build configs MUST enforce deterministic module IDs across environments, guaranteeing identical content hashes given identical source code.

## Bad vs Good Implementations
### Vite 6 Deterministic Chunk Splitting vs Fragile Monolithic Vendor Chunk

#### Bad Antipattern (AI Common Hallucination)
> **Why it fails**: Grouped node_modules into a monolithic 'vendor' chunk creates an unstable boundary. Updating a minor library or changing an imported symbol triggers an edge-wide cache bust for the entire vendor bundle.
```typescript
import { defineConfig } from 'vite';

export default defineConfig({
  build: {
    rollupOptions: {
      output: {
        // ANTI-PATTERN: Lumps all node_modules into a single vendor chunk
        // Any single dependency bump or app-level transitive change invalidates
        // the entire 1MB+ vendor cache across all CDN edge nodes.
        manualChunks(id) {
          if (id.includes('node_modules')) {
            return 'vendor';
          }
        }
      }
    }
  }
});
```

#### Production Standard (Correct)
> **Standard**: Explicit, domain-isolated vendor chunk boundaries guarantee that core runtime dependencies maintain immutable content hashes across application releases, maximizing CDN hit ratios.
```typescript
import { defineConfig } from 'vite';

// Deterministic package-to-chunk isolation mapping
const VENDOR_GROUPS = {
  framework: ['react', 'react-dom'],
  routing: ['react-router-dom', '@remix-run/router'],
  telemetry: ['@datadog/browser-rum', '@sentry/browser']
} as const;

export default defineConfig({
  build: {
    target: 'esnext',
    modulePreload: { polyfill: false },
    rollupOptions: {
      output: {
        entryFileNames: 'assets/entry-[name].[hash].js',
        chunkFileNames: 'assets/chunk-[name].[hash].js',
        assetFileNames: 'assets/[name].[hash].[ext]',
        manualChunks(id) {
          if (!id.includes('node_modules')) return undefined;
          
          for (const [chunkName, packages] of Object.entries(VENDOR_GROUPS)) {
            if (packages.some((pkg) => id.includes(`/node_modules/${pkg}/`))) {
              return `vendor-${chunkName}`;
            }
          }
          // Isolated leaf vendor chunk without cross-contamination
          return undefined;
        }
      }
    }
  }
});
```
Recommended MCP Servers (mcp-serverlist.com)

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

Vite Module Graph Inspector
Analyzes Vite module graph transforms and visualizes chunk boundary relationships to detect hash instability.
Recommended Agent Skills (askills.dev)

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

Bundle Diff Analyzer
Compares chunk hashes across CI build artifacts to audit and verify zero-churn CDN invariant guarantees.
Architectural Specification & Invariant Rationale

Architectural Invariant Design: Deterministic Module Graph Chunk Boundary Invariant in Vite 6

Deterministic Module Graph Chunk Boundary Invariant in Vite 6 defines an industrial-grade behavioral standard for frontend engineering. Enforces strict structural boundary isolation and deterministic content-hashing across Rollup/Rolldown chunks in Vite 6. Eliminates catastrophic cross-chunk cache-invalidation cascades across global CDN layers when incremental business-logic changes occur. 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: Monolithic vendor bundling and unconstrained manualChunks predicates causing global CDN cache bust cascades 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 DriftMonolithic vendor bundling and unconstrained manualChunks predicates causing global CDN cache bust cascadesCritical
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 immutable vendor dependencies (e.g., react, react-dom, lodash-es) into discrete, explicit chunks to preserve CDN edge caching across releases.

Engineers MUST ALWAYS isolate immutable vendor dependencies (e.g., react, react-dom, lodash-es) into discrete, explicit chunks to preserve CDN edge caching across releases.

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 use non-deterministic manualChunks predicate functions that clump dynamic runtime dependencies into arbitrary monolithic chunks.

Engineers MUST NOT use non-deterministic manualChunks predicate functions that clump dynamic runtime dependencies into arbitrary monolithic chunks.

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

Vite output configurations MUST explicitly declare immutable file patterns using `[name].[contenthash].js` or `[name].[hash].js` for entry, chunk, and asset filenames.

Vite output configurations MUST explicitly declare immutable file patterns using `[name].[contenthash].js` or `[name].[hash].js` for entry, chunk, and asset filenames.

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 NEVER permit circular dynamic imports between isolated manual chunks, as this forces Rollup to generate synthetic bridging chunks that destabilize hashes.

Services MUST NEVER permit circular dynamic imports between isolated manual chunks, as this forces Rollup to generate synthetic bridging chunks that destabilize hashes.

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

Build configs MUST enforce deterministic module IDs across environments, guaranteeing identical content hashes given identical source code.

Build configs MUST enforce deterministic module IDs across environments, guaranteeing identical content hashes given identical source code.

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 Deterministic Module Graph Chunk Boundary Invariant in Vite 6 critical for AI coding assistants?

Enforces strict structural boundary isolation and deterministic content-hashing across Rollup/Rolldown chunks in Vite 6. Eliminates catastrophic cross-chunk cache-invalidation cascades across global CDN layers when incremental business-logic changes occur. 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 (Monolithic vendor bundling and unconstrained manualChunks predicates causing global CDN cache bust cascades) 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

Deterministic