vite

Configure and optimize Vite projects including SSR and migration to Vite 8 Rolldown.

302|22|Updated Feb 12, 2026
One-click install
npx skills add https://github.com/JetBrains/skills --skill vite-jetbrains
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: vite
Source: https://github.com/JetBrains/skills/tree/main/vite
Command: npx skills add https://github.com/JetBrains/skills --skill vite-jetbrains

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Vite enables fast, modern frontend development by providing a high-performance dev server, instant module replacement, and an efficient build pipeline, while streamlining SSR workflows and migrations to new bundler features.

Core Features & Use Cases

  • Efficient development server with native ESM and hot module replacement
  • Plugin API for extending build behavior, HTML transforms, and server middleware
  • SSR support and migration guidance for Vite 8 Rolldown

Quick Start

Create a basic vite.config.ts in your project and start the dev server to see live updates.

Frequently Asked Questions about vite

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

FAQPage Schema
How do I configure vite.config.ts for SSR middleware?

Configuring vite.config.ts for SSR middleware involves setting up environment-aware configurations and server middleware. This streamlines SSR workflows by leveraging Vite's native ESM dev server and efficient build pipeline.

What is the best way to migrate to Vite 8 Rolldown?

Migrating to Vite 8 Rolldown requires following specific migration guidance across libraries and SSR apps. This process transitions your build pipeline to the new bundler while retaining existing plugin API extensions and HTML transforms.

Does Vite support library-mode builds and how do I validate them?

Vite supports library-mode builds by allowing you to create and validate them through specific vite.config.ts settings. This uses the Plugin API to extend build behavior and produce efficient, optimized output bundles for libraries.

Can I use the Plugin API to extend HTML transforms in Vite?

You can use the Plugin API to extend HTML transforms in Vite. The API supports extending build behavior, applying HTML transforms, and adding server middleware to fully customize the frontend development pipeline.

Why use Vite for frontend development instead of other build tools?

Use Vite for frontend development to leverage a high-performance dev server, instant hot module replacement, and an efficient build pipeline. It streamlines SSR workflows and provides native ESM support for faster development.

What are the limitations when extending build behavior with the Vite Plugin API?

When extending build behavior with the Vite Plugin API, limitations arise from environment-aware configurations and SSR middleware dependencies. Migrating to Vite 8 Rolldown across libraries requires validating plugin compatibility to avoid build pipeline issues.