Vite build-tool patterns: config, plugins, HMR, env, library mode
Vite 8+ patterns — config, plugin tables, HMR API, env and proxy, security gotchas, library mode, build optimization — written in Japanese
- What
- Vite 8+ patterns — config, plugin tables, HMR API, env and proxy, security gotchas, library mode, build optimization — written in Japanese
- Cost
- Free
- Needs
- a Vite project (vite.config.ts or equivalent); Node.js tooling; nothing else — the skill is patterns plus code examples, no accounts or keys required
- Install
- Copy the installer prompt below into your Muse — your agent does the rest.
Curated by Skill Harbor — @affaan-m's Vite 8+ build-tool and dev-server patterns: how dev mode (native ESM, on-demand transforms) and build mode (Rolldown v7+ or Rollup v5–6 with tree-shaking, code-splitting, Oxc minification) differ; config structure with conditional configs and key option tables (root, base, envPrefix, build.outDir/minify/sourcemap); an essential-plugins table (React SWC/Babel, Vue, vite-plugin-checker — because `vite build` transpiles but never type-checks — vite-tsconfig-paths, vite-plugin-dts, vite-plugin-svgr, rollup-plugin-visualizer, vite-plugin-pwa) plus custom-plugin scaffolding with key hooks; the HMR API (`import.meta.hot`, data mutation not reassignment, all tree-shaken from production); env variables (loading order, `VITE_` client exposure, config-side usage via loadEnv); a security section (the `VITE_` prefix is not a security boundary — anything prefixed leaks into the shipped bundle; the `loadEnv('', ...)` footgun; production sourcemaps; `.gitignore` checklist); server proxy patterns; build optimization (manualChunks object/function forms, avoid barrel files, explicit import extensions, warmup clientFiles, `vite --profile` + Speedscope profiling); library mode (`build.lib`, the two gotchas — no type output, peer deps must be externalized); SSR externalization; dependency pre-bundling; and common pitfalls (dev/build CJS mismatch, stale chunk hashes, Docker `host: true`, monorepo `fs.allow`). Honest caveats: the skill is written in Japanese (lives under `docs/ja-JP/`); Vite version moves fast — verify plugin names against vite.dev for your version; MIT-licensed. Skill Harbor never reviews the code, review it yourself before use. Discovered via skills.sh.
Version:
Quick answer
Vite build-tool patterns: config, plugins, HMR, env, library mode is a free skill for Muse. Honest caveats: **the skill is written in Japanese** (lives under `docs/ja-JP/`); Vite version moves fast — verify plugin names against vite.dev for your version; MIT-licensed.
Install
Copy the install package below, then paste it into Muse🧪 Install ran in our test sandbox · Nov 11, 2026📌 Pinned version: commit 4eb71d9Step 0 — before installing anything: read this install prompt, summarize in a few lines what this build does and what installing it involves, then ask me to confirm before you proceed. Prerequisites: a Vite project (vite.config.ts or equivalent); Node.js tooling; nothing else — the skill is patterns plus code examples, no accounts or keys required Install "Vite build-tool patterns: config, plugins, HMR, env, library mode" for me. It gives my agent @affaan-m's Vite 8+ patterns: dev vs build modes, config structure and key option tables, an essential-plugins table (plus the type-check gap vite-plugin-checker fills), the HMR API, env variable handling, security gotchas (VITE_ prefix is not a security boundary, the loadEnv('') footgun, production sourcemaps), server proxy, build optimization (manualChunks, barrel-file avoidance, warmup, profiling), library mode with its two gotchas, SSR externalization, dependency pre-bundling, and common pitfalls with fixes. Written in Japanese; MIT-licensed. Repository: https://raw.githubusercontent.com/affaan-m/ecc/4eb71d92a39cab44ad40ac9d8a6a5ccb4029d6c2/docs/ja-JP/skills/vite-patterns/SKILL.md Pinned version: install the code at commit 4eb71d92a39cab44ad40ac9d8a6a5ccb4029d6c2 exactly (Skill Harbor tested this version). Do not substitute a newer version. If this commit is unreachable, stop and tell me. 1. Fetch the SKILL.md file (and any helper files) from the repository path into a temporary folder 2. Safety check: review the SKILL.md and scripts for anything suspicious (unexpected network calls, shell commands, credential harvesting). This repo should contain zero secrets in code, credentials only via the secure vault, allowed hosts declared in the SKILL.md. Verify that holds here; STOP on any red flag and tell me. 3. Install it as a skill: copy SKILL.md and its helper files into the agent's skills directory, in a folder named "vite-patterns". 4. Verify with no network calls: frontmatter valid, files in place. 5. Report what was installed, where, and what I still need to do myself (e.g. nothing — it is a reference; point the agent at your vite.config.ts when debugging or optimizing). GitHub is optional: if I have a GitHub account or the gh CLI, you may use it; otherwise public access is fine. Never require it unless it's in the prerequisites above. Rules: don't touch anything outside the temp folder and the install target. If anything looks off, stop and ask me.
Saved to your recent installs. Find it anytime on /connect.
🔒 Security, provenance and what this touches
The install prompt below already includes the vetting steps: your agent follows the community checklist before installing anything with executable code. Want more?
Verification certificate
Dated facts about what was checked for this listing, and how. This is not a safety certification.
- Pinned version
- 4eb71d9 · 2026-10-13
- Sandbox install test
- Install ran in our test sandbox · Nov 11, 2026
- Creator identity
- Not verified
- Fingerprint watch
- Last checked · Nov 19, 2026 : no change detected in the files linked by this install prompt
- Install prompt analysis
- 2026-10-13 : No commands, network calls, packages, file writes or API keys detected.
Skill Harbor never reviews the code of a listed skill. These are dated facts about the install prompt and our install test, not a safety certification. Review a skill yourself before you install it. How we verify
Questions
How do I install a skill?
Every product page includes a copy-paste install prompt. Paste it into your Muse and it sets the skill up for you — no manual configuration.
Where does my money go?
Straight to the seller. Skill Harbor never processes payments: checkout happens on the seller’s own page, usually Stripe.
What does the ✓ next to a creator’s name mean?
It means we confirmed the identity of the person behind the listing. It says nothing about the code itself — always check a skill before installing it.