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-heterogeneous-environment-isolation-standard

Vite 6 Environment API: Heterogeneous Multi-Runtime Isolation & Asset Sandbox Standard

Enforces strict runtime module boundary isolation, deterministic environment-keyed resolution conditions, and sandboxed asset compilation across Edge, Web Worker, SSR, and Client targets using the Vite 6 Environment API. Eliminates shared module graph pollution, illegal native Node/DOM API cross-imports, and leaked execution contexts in federated micro-app architectures.

Prohibited Anti-Pattern: Monolithic Module Resolution and Shared Memory Leaks Across Heterogeneous Runtimes in Vite Builds

Export Ready-to-Drop Configuration

Select format below to copy code or download file directly.

---
description: Vite 6 Environment API: Heterogeneous Multi-Runtime Isolation & Asset Sandbox Standard - Enforces strict runtime module boundary isolation, deterministic environment-keyed resolution conditions, and sandboxed asset compilation across Edge, Web Worker, SSR, and Client targets using the Vite 6 Environment API. Eliminates shared module graph pollution, illegal native Node/DOM API cross-imports, and leaked execution contexts in federated micro-app architectures.
globs: vite.config.{ts,js,mjs}, packages/**/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-heterogeneous-environment-isolation-standard"
---

# Vite 6 Environment API: Heterogeneous Multi-Runtime Isolation & Asset Sandbox Standard

> **Severity**: CRITICAL | **Category**: frontend
> **Anti-Pattern Warning**: Monolithic Module Resolution and Shared Memory Leaks Across Heterogeneous Runtimes in Vite Builds

## System Constraints
You are a Principal Software Architect enforcing the Vite 6 Environment API Heterogeneous Runtime Sandbox Standard. You must rigorously prevent cross-runtime module graph leakage, reject single-target legacy SSR/client hacks, mandate distinct environment pipelines (client, ssr, edge, worker), and guarantee total asset sandboxing across federated micro-apps.

## Strict Guidelines
- Engineers MUST ALWAYS declare isolated runtime configs under the Vite 6 `environments` namespace (e.g., `client`, `ssr`, `edge`, `worker`) instead of relying on legacy monolithic root config properties.
- Engineers MUST NOT share stateful singleton module graphs across different runtime environments; modules intended for multiple targets MUST be resolved distinctly via `environment.name` scoping and target-specific `resolve.conditions`.
- Vite plugins MUST inspect `this.environment.name` or `this.environment.mode` before executing AST transformations, module injections, or asset emits to prevent cross-runtime pollution.
- Federated micro-apps targeting edge runtimes (e.g., Cloudflare Workers, Fastly Compute, Vercel Edge) MUST NOT resolve Node.js built-ins (`node:*`) or browser DOM globals (`document`, `window`); condition-based exports MUST strictly route to edge-safe polyfills or stubs.
- Workers and Edge environments MUST declare their own isolated asset emission policies using custom `output.assetFileNames` boundaries to prevent asset collisions with the client entry graph.
- Components and utilities MUST NEVER use dynamic runtime heuristics like `typeof window !== 'undefined'` as a substitute for environment-level compilation barriers when dealing with runtime-specific SDKs.
- Micro-app federated container manifests MUST register isolated sub-environment manifests, ensuring that shared dependency singletons are evaluated only within their compatible execution context.

## Bad vs Good Implementations
### Vite 6 Configuration: Heterogeneous Environment Sandboxing vs Legacy Shared Config

#### Bad Antipattern (AI Common Hallucination)
> **Why it fails**: Declaring multiple heterogeneous entries (worker, client, ssr) within a legacy single-target build causes condition collisions. 'node' and 'worker' conditions collide, leaking platform-dependent APIs (like node:crypto or DOM access) into incompatible runtimes, and plugins cannot reliably determine which runtime they are transforming.
```typescript
import { defineConfig } from 'vite';

// Anti-pattern: Monolithic config attempting to bundle for client, SSR, and edge simultaneously.
// Node built-ins leak into workers, SSR conditions leak into client, and plugins run indiscriminately.
export default defineConfig({
  resolve: {
    // Leaks edge and node conditions into every runtime compilation
    conditions: ['node', 'worker', 'import', 'browser'],
  },
  ssr: {
    noExternal: ['shared-ui', 'shared-edge-sdk'],
  },
  build: {
    rollupOptions: {
      input: {
        main: './src/index.html',
        worker: './src/worker/entry.ts',
        ssr: './src/entry-server.ts',
      },
    },
  },
});
```

#### Production Standard (Correct)
> **Standard**: Uses the Vite 6 Environment API to create isolated environments ('client', 'ssr', 'edge'). Each runtime defines its own entry points, condition exports, and externalization rules, preventing invalid runtime packages from polluting opposing compilation graphs.
```typescript
import { defineConfig } from 'vite';

// Vite 6 Environment API: Explicit, isolated compilation graphs per runtime
export default defineConfig({
  environments: {
    client: {
      build: {
        outDir: 'dist/client',
        rollupOptions: {
          input: { app: './src/entry-client.tsx' },
        },
      },
      resolve: {
        conditions: ['browser', 'import', 'module'],
      },
    },
    ssr: {
      build: {
        outDir: 'dist/server',
        rollupOptions: {
          input: { server: './src/entry-server.tsx' },
        },
      },
      resolve: {
        conditions: ['node', 'import', 'module'],
        externalConditions: ['node'],
      },
    },
    edge: {
      build: {
        outDir: 'dist/edge',
        rollupOptions: {
          input: { edgeWorker: './src/entry-edge.ts' },
        },
      },
      resolve: {
        conditions: ['edge-light', 'worker', 'import'],
        noExternal: true,
      },
    },
  },
});
```

### Vite Plugin Runtime Context Enforcement

#### Bad Antipattern (AI Common Hallucination)
> **Why it fails**: The plugin does not query the Vite 6 environment lifecycle. It blindly transforms entry files and injects a Node-only telemetry package into client or edge worker graphs, leading to fatal runtime crashes (e.g., 'process is not defined' or 'cannot find module node:async_hooks').
```typescript
import type { Plugin } from 'vite';

// Anti-pattern: Plugin executes indiscriminately across client, ssr, and worker builds
export function injectTelemetryPlugin(): Plugin {
  return {
    name: 'inject-telemetry',
    transform(code, id) {
      if (id.endsWith('entry.ts') || id.endsWith('entry-client.tsx')) {
        // Injects Node-dependent SDK directly into potential client/edge payloads
        return `import { NodeTracing } from '@telemetry/node';\nNodeTracing.init();\n${code}`;
      }
      return null;
    },
  };
}
```

#### Production Standard (Correct)
> **Standard**: Accesses `this.environment.name` within the Vite 6 plugin hook to enforce strict runtime isolation. The plugin deterministically applies target-specific instrumentation, completely avoiding cross-runtime symbol leakage.
```typescript
import type { Plugin } from 'vite';

// Production Guardrail: Environment-aware transformation lifecycle
export function injectTelemetryPlugin(): Plugin {
  return {
    name: 'inject-telemetry',
    transform(code, id) {
      // Vite 6: Query active environment context
      const envName = this.environment.name;

      if (!id.includes('entry')) {
        return null;
      }

      if (envName === 'ssr') {
        return `import { NodeTracing } from '@telemetry/node';\nNodeTracing.init();\n${code}`;
      }

      if (envName === 'edge') {
        return `import { EdgeTracing } from '@telemetry/edge';\nEdgeTracing.init();\n${code}`;
      }

      if (envName === 'client') {
        return `import { BrowserTracing } from '@telemetry/browser';\nBrowserTracing.init();\n${code}`;
      }

      return null;
    },
  };
}
```
Recommended MCP Servers (mcp-serverlist.com)

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

Vite AST Inspector MCP
Analyzes per-environment Vite AST and module resolution graphs to flag cross-runtime dependency leaks.
Recommended Agent Skills (askills.dev)

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

Vite Environment Sandbox Audit
Verifies that multi-environment Vite 6 outputs enforce target isolation and avoid illegal platform imports.
Architectural Specification & Invariant Rationale

Architectural Invariant Design: Vite 6 Environment API: Heterogeneous Multi-Runtime Isolation & Asset Sandbox Standard

Vite 6 Environment API: Heterogeneous Multi-Runtime Isolation & Asset Sandbox Standard defines an industrial-grade behavioral standard for frontend engineering. Enforces strict runtime module boundary isolation, deterministic environment-keyed resolution conditions, and sandboxed asset compilation across Edge, Web Worker, SSR, and Client targets using the Vite 6 Environment API. Eliminates shared module graph pollution, illegal native Node/DOM API cross-imports, and leaked execution contexts in federated micro-app architectures. 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 Module Resolution and Shared Memory Leaks Across Heterogeneous Runtimes in Vite Builds 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 Module Resolution and Shared Memory Leaks Across Heterogeneous Runtimes in Vite BuildsCritical
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 declare isolated runtime configs under the Vite 6 `environments` namespace (e.g., `client`, `ssr`, `edge`, `worker`) instead of relying on legacy monolithic root config properties.

Engineers MUST ALWAYS declare isolated runtime configs under the Vite 6 `environments` namespace (e.g., `client`, `ssr`, `edge`, `worker`) instead of relying on legacy monolithic root config properties.

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 share stateful singleton module graphs across different runtime environments

Engineers MUST NOT share stateful singleton module graphs across different runtime environments; modules intended for multiple targets MUST be resolved distinctly via `environment.name` scoping and target-specific `resolve.conditions`.

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 plugins MUST inspect `this.environment.name` or `this.environment.mode` before executing AST transformations, module injections, or asset emits to prevent cross-runtime pollution.

Vite plugins MUST inspect `this.environment.name` or `this.environment.mode` before executing AST transformations, module injections, or asset emits to prevent cross-runtime pollution.

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

Federated micro-apps targeting edge runtimes (e.g., Cloudflare Workers, Fastly Compute, Vercel Edge) MUST NOT resolve Node.js built-ins (`node

Federated micro-apps targeting edge runtimes (e.g., Cloudflare Workers, Fastly Compute, Vercel Edge) MUST NOT resolve Node.js built-ins (`node:*`) or browser DOM globals (`document`, `window`); condition-based exports MUST strictly route to edge-safe polyfills or stubs.

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

Workers and Edge environments MUST declare their own isolated asset emission policies using custom `output.assetFileNames` boundaries to prevent asset collisions with the client entry graph.

Workers and Edge environments MUST declare their own isolated asset emission policies using custom `output.assetFileNames` boundaries to prevent asset collisions with the client entry graph.

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.
6

Components and utilities MUST NEVER use dynamic runtime heuristics like `typeof window !== 'undefined'` as a substitute for environment-level compilation barriers when dealing with runtime-specific SDKs.

Components and utilities MUST NEVER use dynamic runtime heuristics like `typeof window !== 'undefined'` as a substitute for environment-level compilation barriers when dealing with runtime-specific SDKs.

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.
7

Micro-app federated container manifests MUST register isolated sub-environment manifests, ensuring that shared dependency singletons are evaluated only within their compatible execution context.

Micro-app federated container manifests MUST register isolated sub-environment manifests, ensuring that shared dependency singletons are evaluated only within their compatible execution context.

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: Heterogeneous Multi-Runtime Isolation & Asset Sandbox Standard critical for AI coding assistants?

Enforces strict runtime module boundary isolation, deterministic environment-keyed resolution conditions, and sandboxed asset compilation across Edge, Web Worker, SSR, and Client targets using the Vite 6 Environment API. Eliminates shared module graph pollution, illegal native Node/DOM API cross-imports, and leaked execution contexts in federated micro-app architectures. 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 Module Resolution and Shared Memory Leaks Across Heterogeneous Runtimes in Vite Builds) 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