Configures Vite projects, plugins, SSR builds, and Vite 8 Rolldown migrations.
npx skills add https://github.com/falentio/cimi --skill vite-falentio
Please help me install this Agent Skill. Skill: vite Source: https://github.com/falentio/cimi/tree/main/.agents/skills/vite Command: npx skills add https://github.com/falentio/cimi --skill vite-falentio
vite.config.ts patterns including defineConfig, conditional configs, loadEnv, aliases, proxies, and build targets. - Plugin Authoring: Explains Vite-specific hooks like configureServer, transformIndexHtml, handleHotUpdate, virtual modules, and plugin ordering with enforce. - Build, SSR & Migration: Details library mode, multi-page apps, the JavaScript API, the Vite 6+ Environment API, and migrating from rollupOptions/esbuild to rolldownOptions/oxc in Vite 8. - Use Case: When upgrading a project to Vite 8, use this Skill to rewrite the config from rollupOptions to rolldownOptions and convert esbuild JSX settings to the new oxc option format. ## Quick Start Use the vite skill to migrate my vite.config.ts from rollupOptions to the Vite 8 rolldownOptions format.High-intent search queries and answers about installing and using this skill.
Use the resolve.alias option in vite.config.ts to map shortcuts like '@' to '/src'. Define the config with defineConfig from 'vite' and add entries under resolve.alias for each alias you need.
Rename build.rollupOptions to build.rolldownOptions and replace the esbuild option with the oxc option for JSX and transform settings. For large projects, test first with the rolldown-vite package before upgrading to vite@8.
Implement resolveId and load hooks in your plugin. Prefix the user-facing id with 'virtual:' and the resolved id with '\0', then return the module source string from the load hook.
Vite's SSR support is low-level and intended for meta-framework authors. Application developers should use frameworks like Nuxt, SvelteKit, SolidStart, or TanStack Start, which build on Vite's SSR primitives.
Only variables prefixed with VITE_ are exposed to client code via import.meta.env. Variables without the prefix, like DB_PASSWORD, stay server-side; use loadEnv in vite.config.ts to access them during config resolution.
Most Vite plugins work unchanged because Rolldown supports Rollup's plugin API. If a plugin only works during build, wrap it with enforce: 'post' and apply: 'build' to restrict when it runs.
openwebfScaffold a Vite-based frontend and load it into WebF Go for testing.
sduduzogBuild and deploy full-stack Vue apps with Nuxt SSR and Nitro routes.
Mte90Configure ESLint, Prettier, Jest, and build tools for TypeScript projects.
hieuckConfigure Next.js 16+ to use Turbopack as the default bundler.