vite-v8

Configure, migrate, and debug Vite 8 projects using Rolldown, Oxc, and environment-aware plugin APIs.

Updated Jun 11, 2026
One-click install
npx skills add https://github.com/brillianodhiya/VisionScript --skill vite-v8-brillianodhiya
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: vite-v8
Source: https://github.com/brillianodhiya/VisionScript/tree/main/.agents/skills/vite-v8
Command: npx skills add https://github.com/brillianodhiya/VisionScript --skill vite-v8-brillianodhiya

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires vite, and includes references (resource) components.

What problem does it solve? Vite 8 introduced a major architecture shift to Rolldown and Oxc, and legacy Rollup/esbuild-era configs, plugins, and SSR patterns silently break or underperform when carried forward. This Skill provides the correct Vite 8 config surfaces, migration paths, and debugging mental models so you avoid stale assumptions. ## Core Features & Use Cases - Config Migration: Move vite.config.ts from rollupOptions/esbuild to rolldownOptions/oxc with correct Vite 8 defaults like the Baseline Widely Available build target. - Environment-Aware Plugin Authoring: Write plugins using named environments, this.environment, configEnvironment, hotUpdate, and hook filters for Rust↔JS boundary performance. - SSR and Build Debugging: Troubleshoot runtime issues with Module Runner concepts, ssr.noExternal review, and dev/build parity validation. - Use Case: You are upgrading a project to Vite 8 and the build works but SSR runtime behavior differs by environment. Use this Skill to review environments, externalization boundaries, and Module Runner expectations instead of guessing at bundler flags. ## Quick Start Ask the AI to review or migrate your vite.config.ts to Vite 8 using rolldownOptions and oxc, or to debug a specific SSR, HMR, or plugin issue in your Vite 8 project.

Frequently Asked Questions about vite-v8

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

FAQPage Schema
How do I migrate a Vite config to Vite 8?▼

Migrate to Vite 8 by replacing build.rollupOptions with build.rolldownOptions and esbuild transform settings with oxc. Also review legacy HMR hooks, ssr booleans, and CommonJS interop assumptions, since Vite 8 changed default-import behavior for CJS modules.

How do I write an environment-aware Vite plugin?▼

Write environment-aware Vite plugins using named environments, the configEnvironment hook, and this.environment inside hooks instead of ssr booleans. Add hook filters to transform and resolveId handlers to reduce work crossing the Rust↔JS boundary.

What Node version does Vite 8 require?▼

Vite 8 requires Node.js 20.19+ or 22.12+. The config should be ESM-first, typically a TypeScript vite.config.ts using defineConfig, and CommonJS config is not recommended for new Vite work.

Why does my Vite SSR build behave differently at runtime?▼

SSR runtime differences in Vite 8 are usually environment-boundary issues, not bundling bugs. Review the environments config, this.environment usage, ssr.noExternal externalization decisions, and Module Runner execution expectations before changing bundler settings.

Should I use handleHotUpdate or hotUpdate in Vite 8?▼

Use hotUpdate for new Vite 8 HMR customization because it is the environment-aware direction. handleHotUpdate is legacy-oriented, and building new logic around it produces brittle HMR behavior across runtimes.

When should I not use this Vite 8 guidance?▼

Do not apply this guidance to projects pinned to older Vite release lines, since it assumes the Rolldown/Oxc config surface. Framework-internal issues owned by Next.js or Nuxt and Vitest-specific testing workflows are also out of scope.