vite

Configure Vite projects, plugin APIs, and SSR workflows with Rolldown migration steps.

Updated Apr 5, 2026
One-click install
npx skills add https://github.com/pohlai88/afenda-vite-react --skill vite-pohlai88
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: vite
Source: https://github.com/pohlai88/afenda-vite-react/tree/main/.agents/skills/vite
Command: npx skills add https://github.com/pohlai88/afenda-vite-react --skill vite-pohlai88

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This guide helps developers configure Vite projects, write plugin APIs, and migrate to Vite 8 Rolldown.

Core Features & Use Cases

  • Vite configuration guidance: vite.config.ts, defineConfig, and environment handling
  • Plugin API and SSR workflows: plugin hooks, library builds, and server-side rendering patterns
  • Migration path: Rolldown migration steps and reference topics for modern Vite usage

Quick Start

Configure a Vite project with vite.config.ts and migrate it to Rolldown using the steps provided.

Frequently Asked Questions about vite

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

FAQPage Schema
How do I configure a Vite project using vite.config.ts and defineConfig?

Vite configuration uses defineConfig in vite.config.ts to manage project settings and environment handling. It provides structured setup for build tools, plugin ecosystems, and library builds.

What is the process for Vite Rolldown migration in an existing project?

Vite Rolldown migration involves specific steps to transition your existing build tool setup. The guide provides migration patterns and reference topics to modernize Vite usage effectively.

How do plugin hooks work for Vite server-side rendering workflows?

Vite plugin hooks enable custom SSR workflows by intercepting server-side rendering processes. They integrate with the plugin API to manage library builds and rendering patterns.

Can I use Vite for both application builds and library builds?

Vite supports both application and library builds through its configuration and plugin API. You define build targets and handle environments using vite.config.ts and specific plugin hooks.

Does Vite environment handling support different modes for build tools?

Vite environment handling supports different modes for build tools via defineConfig. It allows you to manage variables and settings dynamically across SSR workflows and plugin ecosystems.

What are the limitations of Vite plugin APIs for server-side rendering?

Vite plugin APIs for SSR require careful hook management to avoid build conflicts. Limitations often involve complex library builds and ensuring plugins correctly handle server-side rendering patterns.