vite

Configure Vite projects with plugin API usage and SSR setup.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Vite project setup and ongoing optimization often require consistent configuration, migration planning, and SSR integration across modern frontend stacks.

Core Features & Use Cases

  • Guidance for configuring vite.config.ts with defineConfig and multi-env support.
  • Migration notes for Vite 8 Rolldown, including changes from esbuild/Rollup to Rolldown.
  • SSR integration and plugin API usage for custom tooling and library builds.

Quick Start

Create a new vite.config.ts that enables fast development and production builds with Rolldown.

Frequently Asked Questions about vite

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

FAQPage Schema
How do I configure Vite for SSR with a multi-environment setup?

Vite SSR setup involves configuring vite.config.ts with defineConfig and multi-env support to handle environment definitions across client-server boundaries. This ensures proper SSR integration and custom tooling.

What changes are needed to migrate a Vite project to the 8 Rolldown build tool?

Migrating to Vite 8 Rolldown requires applying specific migration notes, primarily transitioning your build tool from esbuild/Rollup to Rolldown. This enforces updated configuration patterns for the project.

Can I use the Vite plugin API to build custom tooling and library builds?

Yes, the Vite plugin API can be used for custom tooling and library builds. It enables developers to extend functionality and integrate SSR routes across client-server boundaries.

Does Vite 8 with Rolldown support both fast development and production builds?

Vite 8 with Rolldown supports both fast development and production builds. You can create a vite.config.ts that enables this flexibility while enforcing consistent configuration patterns.

What is the best way to manage environment definitions across client-server boundaries in Vite?

The best way to manage environment definitions across client-server boundaries is by applying Vite's configuration patterns within vite.config.ts using defineConfig and multi-env support.

Why configure vite.config.ts with defineConfig for SSR routes?

Configuring vite.config.ts with defineConfig for SSR routes is necessary to enforce environment definitions and ensure proper integration across client-server boundaries during library and SSR builds.