vite

Configure Vite projects with vite.config.ts, plugins, SSR, and Rolldown migration guidance.

25|3|Updated Mar 3, 2025
One-click install
npx skills add https://github.com/teknokomo/universo-platformo-react --skill vite-teknokomo
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: vite
Source: https://github.com/teknokomo/universo-platformo-react/tree/main/.agents/skills/vite
Command: npx skills add https://github.com/teknokomo/universo-platformo-react --skill vite-teknokomo

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Vite project configuration and migration guidance, including SSR and plugin usage, to streamline setup and updates across libraries and apps.

Core Features & Use Cases

  • Configuration patterns for vite.config.ts, defineConfig usage, and conditional configs
  • Plugin API guidance for extending Vite with custom plugins and ecosystem integration
  • Rolldown migration guidance for Vite 8 and library/SSR workflows

Quick Start

Create a vite.config.ts at your project root and start applying the patterns to configure, build, and migrate your Vite project.

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 library mode and SSR workflows?

Vite configuration uses vite.config.ts with defineConfig to establish conditional patterns for library builds and SSR workflows. Multi-environment setups are specified through core-config and environment-api references to streamline project builds.

What is the best way to extend a Vite build tool with custom plugins?

Vite plugins extend the build tool through the Plugin API, allowing custom ecosystem integration. Guidance covers developing plugins to modify core features and interact with the bundler during application or library builds.

How do I migrate my Vite project to Rolldown for Vite 8?

Rolldown migration for Vite 8 involves transitioning existing library and SSR workflows using the rolldown-migration document. It specifies formal patterns to update bundler configurations and maintain build stability.

Does Vite support multi-environment setups and conditional configs?

Vite supports multi-environment setups through conditional configurations in vite.config.ts. The environment-api document specifies how to apply different build and SSR patterns based on the target deployment context.

When do I need to use defineConfig in my Vite build setup?

DefineConfig is needed in Vite build setups when applying typed, conditional configurations for complex library mode or multi-environment workflows. It provides formal structure to core-config patterns for robust bundler behavior.