dev-vite

Configure Vite projects and plan migrations to Vite 8 with Rolldown/Oxc.

Updated Apr 27, 2026

Search Tags:#migration #build #plugin #config #vite #dev-server

Ready to run

npx skills add https://github.com/Conradmaker/copilot-cockpit --skill dev-vite

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: dev-vite
Source: https://github.com/Conradmaker/copilot-cockpit/tree/main/.github/skills/dev-vite
Command: npx skills add https://github.com/Conradmaker/copilot-cockpit --skill dev-vite

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Vite configuration and migration often require navigating version-specific behavior, plugin boundaries, and SSR considerations; this skill consolidates patterns, references, and migrations into a practical guide to reduce guesswork and accelerate adoption.

Core Features & Use Cases

Provides patterns for vite.config.ts, defineConfig usage, and env handling to stabilize projects.
Offers guidance on library mode, SSR, and Vite 8 migration with a reference-led approach for teams adopting Rolldown/Oxc tooling.
Use Case: When starting a new Vite project or upgrading an existing one, consult this skill to decide on config structure and plugin usage before coding.

Quick Start

Follow this skill to configure Vite with best practices and plan a safe migration path for your project.

Frequently Asked Questions about dev-vite

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

FAQPage Schema

How do I configure Vite using vite.config.ts and defineConfig?▼

Vite configuration with vite.config.ts and defineConfig is stabilized by applying established patterns for environment variable handling and plugin boundaries to reduce guesswork in modern projects. This approach consolidates core config structures into a practical reference guide.

What is the best way to plan a Vite 8 migration with Rolldown and Oxc?▼

A Vite 8 migration with Rolldown and Oxc tooling is planned using a reference-led approach that outlines migration readiness and core patterns. This ensures teams adopting new build tooling can safely navigate version-specific behavior and plugin boundaries.

Can I use Vite library mode and SSR in the same project?▼

Vite library mode and SSR can be used in the same project by following consolidated patterns for development server behavior and build outputs. This skill outlines core structural configurations to address both server-side rendering and library packaging needs simultaneously.

When do I need to simplify my Vite config structure?▼

Vite config structure simplification is needed when navigating version-specific behavior, plugin boundaries, or SSR considerations becomes too complex. Consolidating patterns and references into a practical guide reduces guesswork and accelerates project adoption.

Does Vite plugin usage change during a major version migration?▼

Vite plugin usage can change during a major version migration due to shifting plugin boundaries and version-specific behavior. Consulting a reference-led migration guide helps decide on plugin structure and configuration patterns before coding begins.

Why does my dev-server behavior differ after updating Vite?▼

Dev-server behavior may differ after updating Vite due to version-specific changes in configuration handling and plugin boundaries. Applying consolidated configuration patterns and environment handling references stabilizes the updated development server.