vite

Configure Vite build tooling, plugins, SSR, and Rolldown migration for frontend projects.

Updated Sep 17, 2026
One-click install
npx skills add https://github.com/juanjaragavi/utilities-manager --skill vite-juanjaragavi
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: vite
Source: https://github.com/juanjaragavi/utilities-manager/tree/main/.agents/skills/vite
Command: npx skills add https://github.com/juanjaragavi/utilities-manager --skill vite-juanjaragavi

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Frontend developers working with Vite often struggle with scattered configuration knowledge across config files, plugin APIs, SSR setup, and the breaking changes introduced by Vite 8's Rolldown bundler. This Skill consolidates authoritative Vite guidance into one place so you get correct, version-aware answers immediately. ## Core Features & Use Cases - Configuration Guidance: Covers vite.config.ts, defineConfig, conditional configs, loadEnv, aliases, proxies, and build targets. - Plugin Authoring: Explains Vite-specific hooks like configResolved, configureServer, transformIndexHtml, virtual modules, and plugin ordering. - Build, SSR & Migration: Documents library mode, multi-page apps, the JavaScript API, the Vite 6+ Environment API, and the Vite 8 Rolldown/Oxc migration path. - Use Case: You are upgrading a project from Vite 7 to Vite 8 and need to convert rollupOptions to rolldownOptions and esbuild settings to oxc — this Skill provides the exact before/after config patterns. ## Quick Start Ask the assistant to help you write or migrate a vite.config.ts for your project, for example to set up path aliases, a dev proxy, or upgrade to Vite 8 Rolldown options.

Frequently Asked Questions about vite

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

FAQPage Schema
How do I configure path aliases in vite.config.ts?▼

Use the resolve.alias option in vite.config.ts to map shortcuts like "@" to "/src". Define the config with defineConfig from Vite, and prefer TypeScript config files for type checking and editor intellisense.

How do I migrate from Vite 7 to Vite 8 Rolldown?▼

Rename rollupOptions to rolldownOptions and replace the esbuild option with the oxc option in your config. For large projects, test first with the rolldown-vite package, then upgrade to vite@8 once stable.

How do I create a Vite plugin with virtual modules?▼

Implement resolveId and load hooks: resolve a user-facing id prefixed with "virtual:" to an internal id prefixed with "\0", then return the module source from load. Use the enforce property to control plugin ordering relative to core plugins.

Does Vite expose all environment variables to the client?▼

No, only variables prefixed with VITE_ are exposed to client code via import.meta.env. Other variables stay server-side; use loadEnv in vite.config.ts to read env files during config resolution.

When should I use Vite SSR directly versus a meta-framework?▼

Vite's SSR support is low-level and intended for framework authors. Application developers should use meta-frameworks like Nuxt, SvelteKit, SolidStart, or TanStack Start, which build on Vite's SSR primitives.