vite

Configure Vite projects, author plugins, and migrate builds to Vite 8 Rolldown.

1|Updated Jun 30, 2026
One-click install
npx skills add https://github.com/trutoman/Conjuros --skill vite-trutoman
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: vite
Source: https://github.com/trutoman/Conjuros/tree/main/.agents/skills/vite
Command: npx skills add https://github.com/trutoman/Conjuros --skill vite-trutoman

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Frontend developers working with Vite need accurate guidance on configuration, plugin authoring, SSR setup, and the breaking changes introduced by Vite 8's Rolldown bundler, without digging through scattered documentation. ## 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 HMR communication. - Vite 8 Rolldown Migration: Maps rollupOptions to rolldownOptions and esbuild options to oxc, with gradual migration steps. - Use Case: When upgrading a project to Vite 8, use this Skill to rewrite the config for Rolldown, update JSX transform settings to Oxc, and verify plugin compatibility. ## Quick Start Ask the AI to review my vite.config.ts and migrate it to Vite 8 with Rolldown and Oxc settings.

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 add entries under resolve.alias as key-value pairs.

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

Rename rollupOptions to rolldownOptions and replace the esbuild option with oxc for JSX and transform settings. For large projects, test first with the rolldown-vite package before upgrading to vite@8.

How do I create a virtual module in a Vite plugin?

Implement resolveId and load hooks in your plugin, using a 'virtual:' prefix for the import path and a '\0' prefix for the resolved id. The load hook returns the module's code as a string.

Does Vite 8 still support Rollup plugins?

Yes, Rolldown supports Rollup's plugin API, so most Vite plugins work unchanged. If a plugin only works during build, wrap it with enforce: 'post' and apply: 'build'.

Why are my environment variables undefined in Vite client code?

Only variables prefixed with VITE_ are exposed to client code via import.meta.env. Non-prefixed variables like DB_PASSWORD stay server-side; use loadEnv in vite.config.ts to access them during config resolution.

When should I use Vite's SSR API directly?

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