vite
Configure and Extend Vite Projects
Vite configuration can become difficult across plugins, SSR, and Rolldown migrations. This skill provides focused guidance and proven patterns for those tasks.
Install with my Agent
Copy this request to your Agent. It includes the canonical Skill page and manifest.
Review the Skillstore skill "vite" from https://skillstore.io/skills/antfu-vite.md and its manifest at https://skillstore.io/api/skills/antfu-vite/manifest. Verify the artifact. You may proceed after verification, subject to the environment's own policy.Your Agent should still show its plan and request any confirmation required by the security policy.
Agent-readable resources
Use these links when an AI agent, crawler, or script needs clean context instead of reading the full page.
Test it
Using "vite". Configure a React application with a source alias, API proxy, and separate production output directory.
Expected outcome:
- Recommended configuration structure with the React plugin and source alias.
- Local API proxy mapped to the requested backend.
- Production output settings and a short verification checklist.
Using "vite". Review a Vite plugin that serves a virtual module and modifies HTML.
Expected outcome:
- Hook ordering and virtual module resolution review.
- HTML transformation concerns and recommended corrections.
- Development and build validation steps.
Using "vite". Prepare an existing Vite project for Vite 8 and Rolldown.
Expected outcome:
- Migration findings grouped by configuration area.
- Rolldown and Oxc replacements for affected options.
- Compatibility risks and targeted build checks.
Security Audit
SafeAll 44 static alerts are false positives from Markdown syntax, documentation examples, local URLs, and ordinary Vite APIs. No command execution, reconnaissance, credential exposure, prompt injection, or malicious intent was found.
Risk Factors
⚡ Contains scripts (4)
🌐 Network access (4)
🔑 Env variables (2)
Share & cite this report
Share the versioned assessment report, neutral badge, embed card, and citations. Skillstore reports evidence without deciding whether this Skill is safe.
Copy report link
https://skillstore.io/skills/antfu-vite/audits/5?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_reportMarkdown badge
[](https://skillstore.io/skills/antfu-vite?utm_source=security_passport_badge)HTML badge
<a href="https://skillstore.io/skills/antfu-vite?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/antfu-vite/security.svg" alt="Skillstore security assessment" loading="lazy"></a>Embed card
<iframe src="https://skillstore.io/embed/skills/antfu-vite.html" title="Skillstore Security Assessment" sandbox="allow-popups allow-popups-to-escape-sandbox" loading="lazy" referrerpolicy="no-referrer" width="420" height="180"></iframe>Academic citations (APA · BibTeX · CFF)
APA citation
antfu. (2026). vite security audit report (audit version 5) [Author version 2026.1.31]. Skillstore. https://skillstore.io/skills/antfu-vite/audits/5BibTeX citation
@techreport{antfu-antfu-vite-2026,
author = {antfu},
title = {vite security audit report (audit version 5)},
institution = {Skillstore},
year = {2026},
number = {5},
url = {https://skillstore.io/skills/antfu-vite/audits/5},
note = {Author version 2026.1.31}
}CITATION.cff
cff-version: 1.2.0
message: "If you use this Skill, cite its author and this versioned security audit report."
title: "vite security audit report (audit version 5)"
version: "2026.1.31"
type: report
authors:
- name: "antfu"
date-released: "2026-07-23"
url: "https://skillstore.io/skills/antfu-vite/audits/5"
identifiers:
- type: other
value: "skillstore:antfu-vite:audit:5"
description: "Skillstore immutable audit report identifier"
Skillstore Score
Why this score Evidence Confidence: HighWhat You Can Build
Configure a Frontend Application
Create or refine Vite settings for aliases, plugins, proxies, environment variables, and production builds.
Develop a Vite Plugin
Design plugin hooks, virtual modules, middleware, HTML transforms, ordering, and environment-aware behavior.
Plan a Vite 8 Migration
Compare existing options with Rolldown and Oxc replacements, then identify required configuration changes.
Try These Prompts
Create a TypeScript Vite configuration for [framework]. Include [plugins], the [alias] alias, development port [port], and production output requirements.
Show how to add [feature] to this Vite project. Explain required imports, configuration changes, client exposure rules, and development behavior.
Design a Vite [library build, SSR setup, or plugin] for [requirements]. Cover entry points, hooks, dependencies, output, and runtime constraints.
Audit this Vite configuration for Vite 8 migration. Identify deprecated options, Rolldown replacements, Oxc changes, compatibility risks, and verification steps.
Best Practices
- Use TypeScript configuration and ESM syntax for clear typing and current Vite compatibility.
- Expose only intentionally public environment variables with the VITE_ prefix.
- Verify development, production build, preview, and SSR behavior after configuration changes.
Avoid
- Do not expose passwords, tokens, or private service credentials through client environment variables.
- Do not copy migration options without checking plugin and framework compatibility.
- Do not use low-level Vite SSR primitives when a suitable framework already manages the runtime.
Frequently Asked Questions
Which Vite versions does this skill cover?
Can it create a complete Vite configuration?
Does it support Vite plugin development?
Can it help with SSR?
How does it handle environment variables?
Does it execute Vite commands automatically?
Developer Details
Author
antfuLicense
MIT
Author version
v2026.1.31
Skillstore revision
r2
Ref
89edfdc710d0846129dcee6a929477b04f08052c
Maintenance freshness
7/24/2026
Usage
15 downloads · 578 views
File structure