vite-impl-migration

Outline Vite 5-to-8 migration steps with config and plugin changes.

4|Updated Mar 20, 2026
One-click install
npx skills add https://github.com/OpenAEC-Foundation/OpenAEC-Workspace-Composer --skill vite-impl-migration
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: vite-impl-migration
Source: https://github.com/OpenAEC-Foundation/OpenAEC-Workspace-Composer/tree/main/.claude/skills/vite/vite-impl/vite-impl-migration
Command: npx skills add https://github.com/OpenAEC-Foundation/OpenAEC-Workspace-Composer --skill vite-impl-migration

SYSTEM DOCUMENTATION & REQUIREMENTS

## What problem does it solve? Vite upgrades across major versions introduce breaking changes that disrupt projects and plugin compatibility, making manual migration error-prone.

## Core Features & Use Cases This migration guide provides a step-by-step path for upgrading Vite from 5 through 8, including environment checks, config key migrations (rollupOptions to rolldownOptions), dependency alignment, and actionable scenarios for plugin authors and project maintainers.

### Quick Start Follow the recommended incremental path to upgrade through Vite major versions, validating Node.js compatibility, updating config keys, and aligning plugins at each step.

Frequently Asked Questions about vite-impl-migration

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

FAQPage Schema
How do I migrate Vite config from rollupOptions to rolldownOptions?

Migrate Vite config by replacing rollupOptions with rolldownOptions to align with the Rolldown transition, ensuring your build configuration targets the correct build outputs for newer Vite major versions.

What Node.js version do I need for a Vite major version upgrade?

A Vite major version upgrade requires validating Node.js environment compatibility through specific environment checks, ensuring your setup meets the baseline before proceeding with the stepwise migration path.

What are the breaking changes when upgrading Vite from 5 to 8?

Breaking changes when upgrading Vite from 5 to 8 include Sass/esbuild/rollup to Rolldown transitions, updated config keys, modified build targets, and adjusted plugin hooks that require explicit compatibility checks across your project.

How do I handle plugin compatibility during a Vite migration?

Handle plugin compatibility during Vite migration by performing explicit compatibility checks for plugin hooks and applying actionable dependency alignment scenarios for both plugin authors and project maintainers.

What is the best way to safely upgrade Vite across multiple major versions?

The best way to safely upgrade Vite is following a recommended incremental path, validating Node.js compatibility, updating config keys, and aligning plugins at each stepwise major version transition.

Does Vite migration support transitioning from esbuild and rollup to Rolldown?

Yes, Vite migration supports transitioning from esbuild and rollup to Rolldown by outlining required environment checks, build target mappings, and config modifications to ensure functional continuity across major versions.