AgentRules.org
RulesStacksClientsAuditorPrunerSelf-HealRFCsBenchmarkCLICI/CDAuthorsSubmit
This specification is maintained by the AgentRules Working Group. Have enhancements or want to claim maintainership?Submit Specification →
devopscritical PriorityID: vite6-environment-api-multi-runtime-isolation-vite-6-environme-118

Vite 6 Environment API Multi-Runtime Pipeline Isolation

Architects strictly isolated compilation graphs and Hot Module Replacement (HMR) transports across heterogeneous runtimes (Workerd, Node.js, Bun, and Browser) within Vite 6. Prevents runtime pollution, leaked globals, and dual-package hazards by enforcing per-environment build, runner, and resolution boundary configurations.

Prohibited Anti-Pattern: Global Resolution Leaking and Legacy ssrLoadModule Cross-Contamination Across Heterogeneous Target Runtimes

Export Ready-to-Drop Configuration

Select format below to copy code or download file directly.

---
description: Vite 6 Environment API Multi-Runtime Pipeline Isolation - Architects strictly isolated compilation graphs and Hot Module Replacement (HMR) transports across heterogeneous runtimes (Workerd, Node.js, Bun, and Browser) within Vite 6. Prevents runtime pollution, leaked globals, and dual-package hazards by enforcing per-environment build, runner, and resolution boundary configurations.
globs: **/vite.config.{ts,js,mjs}, apps/**/vite.config.{ts,js,mjs}, packages/**/vite.config.{ts,js,mjs}
alwaysApply: true
verified_by: "agentrules.org"
license: "CC-BY-4.0"
source: "https://agentrules.org/rules/vite6-environment-api-multi-runtime-isolation-vite-6-environme-118"
---

# Vite 6 Environment API Multi-Runtime Pipeline Isolation

> **Severity**: CRITICAL | **Category**: devops
> **Anti-Pattern Warning**: Global Resolution Leaking and Legacy ssrLoadModule Cross-Contamination Across Heterogeneous Target Runtimes

## System Constraints
You are a Principal Software Architect enforcing Vite 6 Environment API Multi-Runtime Pipeline Isolation. Vite 6 deprecates monolithic SSR configurations in favor of first-class `environments` objects with isolated module graphs, module runners, and resolve conditions. You must enforce that builds targeting diverse runtimes (e.g., Cloudflare Workerd edge, Node.js SSR, and browser DOM) maintain completely partitioned compilation contexts, dedicated HMR channels, and zero leaking of platform built-in mocks across boundaries.

## Strict Guidelines
- Engineers MUST ALWAYS configure distinct environments inside `environments.<name>` rather than using top-level `ssr` overrides or legacy `server.ssrLoadModule`.
- Engineers MUST NOT leak Node.js platform polyfills or globals into edge environments (e.g., Cloudflare Workerd); edge environments MUST set `resolve.conditions: ['workerd', 'worker', 'browser']` and disable Node built-in resolution.
- Code SHOULD leverage the Vite 6 Module Runner API (`createModuleRunner` / `RunnableDevEnvironment`) when executing code in external runtimes, passing transport channels instead of executing code in the parent Node process.
- Services MUST configure decoupled `build.outDir` targets per environment using the Vite 6 `builder` API (`builder.buildApp`) to prevent write collisions and duplicate asset hashes.
- Plugins MUST target specific environments using `applyToEnvironment(environment)` or conditional hooks (`hot.send` routed strictly through `environment.hot`) rather than broadcasting across all runtime graphs.

## Bad vs Good Implementations
### Configuring Multi-Runtime Environment Isolation in Vite 6

#### Bad Antipattern (AI Common Hallucination)
> **Why it fails**: Configuring global resolve conditions conflates Node, Edge (Workerd), and Browser targets. Modules resolving platform primitives (like 'node:crypto' or 'cloudflare:sockets') leak into incompatible contexts. It also relies on deprecated Vite 5 top-level SSR settings.
```typescript
import { defineConfig } from 'vite';

// ANTI-PATTERN: Vite 4/5 legacy monolithic approach polluting resolve conditions
// and attempting to build Node and Cloudflare Workers in a shared context.
export default defineConfig({
  resolve: {
    // Leaks workerd condition to client and node runtime builds
    conditions: ['workerd', 'node', 'import']
  },
  ssr: {
    target: 'webworker',
    noExternal: true
  },
  build: {
    outDir: 'dist',
    rollupOptions: {
      // Hardcoded single-target bundle
      input: './src/entry-server.ts'
    }
  }
});
```

#### Production Standard (Correct)
> **Standard**: Employs Vite 6 Environment API to create isolated compilation graphs for 'client', 'ssr' (Node.js), and 'edge' (Workerd). Each environment enforces explicit `resolve.conditions`, independent output paths, and coordinated parallel compilation via `builder.buildApp`.
```typescript
import { defineConfig } from 'vite';
import { cloudflare } from '@cloudflare/vite-plugin';

// PRODUCTION STANDARD: Vite 6 Environment API with partitioned module graphs
export default defineConfig({
  environments: {
    client: {
      consumer: 'client',
      build: {
        outDir: 'dist/client'
      }
    },
    ssr: {
      consumer: 'server',
      resolve: {
        conditions: ['node', 'import'],
        externalConditions: ['node']
      },
      build: {
        outDir: 'dist/server',
        ssr: true
      }
    },
    edge: {
      consumer: 'server',
      resolve: {
        noExternal: true,
        conditions: ['workerd', 'worker', 'browser'],
        externalConditions: ['workerd']
      },
      build: {
        outDir: 'dist/edge',
        ssr: true
      }
    }
  },
  builder: {
    async buildApp(builder) {
      await Promise.all([
        builder.build(builder.environments.client),
        builder.build(builder.environments.ssr),
        builder.build(builder.environments.edge)
      ]);
    }
  }
});
```
Recommended MCP Servers (mcp-serverlist.com)

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

Vite Monorepo Module Graph Inspector
Inspects Vite 6 runtime environment module graphs, detecting circular dependencies and cross-environment condition leaks.
Recommended Agent Skills (askills.dev)

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

Vite 6 Environment Configuration Auditor
Validates Vite 6 configurations to guarantee runtime separation between Workerd, Node, and browser pipelines.
Architectural Specification & Invariant Rationale

Architectural Invariant Design: Vite 6 Environment API Multi-Runtime Pipeline Isolation

Vite 6 Environment API Multi-Runtime Pipeline Isolation defines an industrial-grade behavioral standard for devops engineering. Architects strictly isolated compilation graphs and Hot Module Replacement (HMR) transports across heterogeneous runtimes (Workerd, Node.js, Bun, and Browser) within Vite 6. Prevents runtime pollution, leaked globals, and dual-package hazards by enforcing per-environment build, runner, and resolution boundary configurations. 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: Global Resolution Leaking and Legacy ssrLoadModule Cross-Contamination Across Heterogeneous Target Runtimes 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 DriftGlobal Resolution Leaking and Legacy ssrLoadModule Cross-Contamination Across Heterogeneous Target RuntimesCritical
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 configure distinct environments inside `environments.<name>` rather than using top-level `ssr` overrides or legacy `server.ssrLoadModule`.

Engineers MUST ALWAYS configure distinct environments inside `environments.<name>` rather than using top-level `ssr` overrides or legacy `server.ssrLoadModule`.

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 leak Node.js platform polyfills or globals into edge environments (e.g., Cloudflare Workerd)

Engineers MUST NOT leak Node.js platform polyfills or globals into edge environments (e.g., Cloudflare Workerd); edge environments MUST set `resolve.conditions: ['workerd', 'worker', 'browser']` and disable Node built-in resolution.

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 leverage the Vite 6 Module Runner API (`createModuleRunner` / `RunnableDevEnvironment`) when executing code in external runtimes, passing transport channels instead of executing code in the parent Node process.

Code SHOULD leverage the Vite 6 Module Runner API (`createModuleRunner` / `RunnableDevEnvironment`) when executing code in external runtimes, passing transport channels instead of executing code in the parent Node process.

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 configure decoupled `build.outDir` targets per environment using the Vite 6 `builder` API (`builder.buildApp`) to prevent write collisions and duplicate asset hashes.

Services MUST configure decoupled `build.outDir` targets per environment using the Vite 6 `builder` API (`builder.buildApp`) to prevent write collisions and duplicate asset 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

Plugins MUST target specific environments using `applyToEnvironment(environment)` or conditional hooks (`hot.send` routed strictly through `environment.hot`) rather than broadcasting across all runtime graphs.

Plugins MUST target specific environments using `applyToEnvironment(environment)` or conditional hooks (`hot.send` routed strictly through `environment.hot`) rather than broadcasting across all runtime graphs.

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 Environment API Multi-Runtime Pipeline Isolation critical for AI coding assistants?

Architects strictly isolated compilation graphs and Hot Module Replacement (HMR) transports across heterogeneous runtimes (Workerd, Node.js, Bun, and Browser) within Vite 6. Prevents runtime pollution, leaked globals, and dual-package hazards by enforcing per-environment build, runner, and resolution boundary configurations. 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 (Global Resolution Leaking and Legacy ssrLoadModule Cross-Contamination Across Heterogeneous Target Runtimes) 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 DEVOPS Rules

View all rules →
devops
86

Kubernetes Gateway API v1 HTTPRoute Canary and ReferenceGrant Invariants

Enforces strict conformance to Kubernetes Gateway API v1 specifications during migration from legacy Ingress controllers. Mandates explicit ReferenceGrant resources for cross-namespace routing, strict relative integer weighting for HTTPRoute canary releases, and explicit backendRef port declarations.

devops
118

ArgoCD ApplicationSet Matrix Generator Invariants & Cascade Deletion Guards

Enforces strict structural constraints on ArgoCD ApplicationSet Matrix generators combining cluster selectors and Git directories. Prevents catastrophic multi-cluster cascade pruning, accidental secret exposure through parameter interpolation, and runaway Application CR explosion via explicit sync policies, preservation finalizers, and parameter validation.

devops
40

Karpenter Resilient Topology, Interruption Queue, and Consolidation Budget Standard

Enforces deterministic disruption budgets, multi-instance-type diversification, and event-driven SQS interruption queue handling across Karpenter NodePools and EC2NodeClasses. Eliminates cascading eviction loops, instance starvation, and availability downtime during AWS Spot rebalances and underutilized node consolidation.

1 Rule in Stack

Vite