Astro and Vite question

[past vine]

Hi @quiet hollow. I'm kapa.ai, your friendly support bot. I will try to answer your question by searching through the knowledge base. :wave:

---

Astro relies heavily on Vite as its underlying development server and build tool. Astro builds on top of Vite, using it for both development and production bundling. Many advanced configurations and plugin support in Astro are achieved by passing options directly to Vite or by using Vite and Rollup plugins within the Astro configuration. For example, you can add custom Vite plugins directly in your astro.config.mjs file, and Astro exposes hooks for integrations that allow you to modify the Vite config or inject plugins at various stages of the build process Extending file type support Installing a Vite or Rollup plugin Configuration Reference: vite.

Astro does implement its own processing pipeline for features unique to Astro (such as its component syntax, routing, and content processing), but this pipeline is layered on top of Vite rather than replacing it. The integration API and hooks (like astro:config:setup, astro:build:setup, etc.) are designed to feel familiar to those who have written Vite or Rollup plugins, and they often interact directly with Vite’s configuration and plugin system Building Your Own Integration Integration API Reference.

In summary, Astro is not just a collection of Vite plugins; it provides its own higher-level features and abstractions, but it fundamentally depends on Vite for much of its build and development workflow. If you are using Vite-specific plugins, configuration, or APIs, you interact with them through Astro’s Vite integration points Configuration Reference: vite.

Note: you can ask me a follow up question by @ mentioning me again :speech_balloon: