vite-core-architecture

Clarify Vite's two-mode architecture covering dev server and production build internals.

3|Updated Mar 19, 2026
One-click install
npx skills add https://github.com/Impertio-Studio/Vite-Claude-Skill-Package --skill vite-core-architecture-impertio-studio
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: vite-core-architecture
Source: https://github.com/Impertio-Studio/Vite-Claude-Skill-Package/tree/main/skills/source/vite-core/vite-core-architecture
Command: npx skills add https://github.com/Impertio-Studio/Vite-Claude-Skill-Package --skill vite-core-architecture-impertio-studio

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Clarifies Vite's two-mode architecture and internals, helping users distinguish between the development dev server and production build.

Core Features & Use Cases

  • Two-mode architecture guidance: dev server uses native ESM, production uses Rolldown/Rollup.
  • Internal tooling evolution: esbuild to Oxc, Rollup to Rolldown, and pre-bundling details.
  • Index.html as entry point and module graph / pre-bundling behaviors.

Quick Start

Study the vite-core-architecture guide to understand how Vite serves modules in development and bundles in production.

Frequently Asked Questions about vite-core-architecture

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How does Vite's dev server architecture differ from its production build?

Vite uses a two-mode architecture where the dev server serves native ESM modules, while production builds bundle modules using Rolldown or Rollup for optimized output.

What is pre-bundling in Vite and how does the module graph handle it?

Pre-bundling in Vite processes dependencies using esbuild to optimize them before serving. The module graph tracks these relationships to manage native ESM loading during development.

Why is index.html required as the entry point in Vite architecture?

Index.html serves as the entry point in Vite architecture because the dev server parses it to identify module scripts, establishing the initial module graph for serving native ESM.

How does Vite's internal tooling transition from esbuild and Rollup to Oxc and Rolldown?

Vite's internal tooling evolves from esbuild to Oxc for faster parsing and from Rollup to Rolldown, integrating Rust-based performance improvements across its two-mode architecture.

When do I need to understand Vite's two-mode architecture for my workflow?

Understanding Vite's two-mode architecture is needed when distinguishing dev server behaviors like native ESM from production workflows involving pre-bundling and Rolldown bundling.