claude-craft / vite
CLAUDE.md108 starsChanged 17 days agoMITView on GitHub
⚠️ Tier-3 / Community — This stack is community-maintained and scoped strictly to framework-agnostic Vite usage. It does not cover React/Vue/Angular/Svelte's own Vite dev-server integration — those are documented in each stack's own tooling.md (@.claude/references/react/, @.claude/references/vuejs/, @.claude/references/angular/, @.claude/references/svelte/). Scope framework-agnostic uniquement. Pour Vite en tant que dev-server React/Vue/Angular/Svelte, voir le tooling.md de ce stack. Source : Vite 8 blog | Rolldown Vite n'a pas de modèle de composant propre — c'est un build tool et un dev server. Ce stack…
In this repository61 other files it gives its agents.
- docs/AGENTS.mdAGENTS.md
- .claude/CLAUDE.mdCLAUDE.md
- .claude/references/angular/CLAUDE.mdCLAUDE.md
- .claude/references/flutter/CLAUDE.mdCLAUDE.md
- .claude/references/laravel/CLAUDE.mdCLAUDE.md
- .claude/references/paperclip/CLAUDE.mdCLAUDE.md
- .claude/references/reactnative/CLAUDE.mdCLAUDE.md
- .claude/references/svelte/CLAUDE.mdCLAUDE.md
- .claude/references/symfony/CLAUDE.mdCLAUDE.md
- .claude/references/vuejs/CLAUDE.mdCLAUDE.md
- aggregatesSkill
- api-gatewaySkill
- architectSkill
- architecture-clean-dddSkill
- architectureSkill
- asyncSkill
- atomic-tasksSkill
- coding-standardsSkill
- cqrsSkill
- ddd-patternsSkill
- debug-methodicalSkill
- design-md-conventionSkill
- docker-hadolintSkill
- doctrine-extensionsSkill
- documentationSkill
- domain-eventsSkill
- dynamic-workflowsSkill
- ecosystem-toolsSkill
- edge-computingSkill
- event-drivenSkill
- git-workflowSkill
- graphqlSkill
- i18nSkill
- kiss-dry-yagniSkill
- monorepoSkill
- multitenantSkill
- navigationSkill
- observabilitySkill
- parallel-worktreesSkill
- performanceSkill
- quality-toolsSkill
- remotionSkill
- security-flutterSkill
- security-reactnativeSkill
- security-reactSkill
- securitySkill
- security-symfonySkill
- socratic-brainstormSkill
- solid-principlesSkill
- state-managementSkill
- sub-agents-patternsSkill
- testing-flutterSkill
- testing-pythonSkill
- testing-reactnativeSkill
- testing-reactSkill
- testingSkill
- testing-symfonySkill
- toolingSkill
- value-objectsSkill
- wasmSkill
- The first 60 shown.
The file
Files
Vite 8.3 (framework-agnostic) - Quick Reference
⚠️ Tier-3 / Community — This stack is community-maintained and scoped strictly to framework-agnostic Vite usage. It does not cover React/Vue/Angular/Svelte's own Vite dev-server integration — those are documented in each stack's own
tooling.md(@.claude/references/react/,@.claude/references/vuejs/,@.claude/references/angular/,@.claude/references/svelte/).
Scope framework-agnostic uniquement. Pour Vite en tant que dev-server React/Vue/Angular/Svelte, voir le tooling.md de ce stack.
Versions Requises (2026)
| Composant | Version | Notes |
| Vite | 8.3.x | Rolldown bundler par défaut (voir rolldown.md) |
| TypeScript | 5.6+ | Strict mode obligatoire |
| Vitest | 4.1+ | Browser Mode stable pour workers/WASM |
| Node.js | ^20.19.0 ou >=22.12.0 | Prérequis de Vite 8 (engines) |
| vite-plugin-dts | 5.x | Génération .d.ts pour build.lib |
Source : Vite 8 blog | Rolldown
Ce que couvre ce stack
Vite n'a pas de modèle de composant propre — c'est un build tool et un dev server. Ce stack documente les 4 usages framework-agnostic de Vite :
| Shape | Description | Doc |
| Vanilla SPA | index.html comme point d'entrée source, TypeScript/JS pur ou Web Components (Lit) | architecture.md §1 |
| Library authoring | build.lib + vite-plugin-dts, publication npm ESM/CJS | architecture.md §2 |
| Multi-page app (MPA) | top-level input avec plusieurs entrées HTML | architecture.md §3 |
| Workers / WASM | Entrées ?worker, ?worker&inline, modules WebAssembly | architecture.md §4 |
Hors scope (explicitement)
- Intégration Vite comme dev-server pour React (
@vitejs/plugin-react) → voir@.claude/references/react/ - Intégration Vite comme dev-server pour Vue.js (
@vitejs/plugin-vue) → voir@.claude/references/vuejs/ - Intégration Vite comme dev-server pour Angular (
@angular/buildbasé sur esbuild/Vite) → voir@.claude/references/angular/ - Intégration Vite comme dev-server pour Svelte/SvelteKit (
@sveltejs/vite-plugin-svelte) → voir@.claude/references/svelte/
Ce stack ne documente aucun modèle de composant (pas de JSX, pas de SFC, pas de runes) — uniquement la configuration de build, les entrées, les plugins et l'outillage Vite lui-même.
Points clés 2026
Vite 8 — Rolldown par défaut
Depuis Vite 8, Rolldown (port Rust de Rollup, par l'équipe Vite/VoidZero) remplace esbuild comme bundler de production par défaut. Build 3-5× plus rapide, API de configuration largement compatible avec rollupOptions historique (déprécié depuis Vite 8 au profit de rolldownOptions) — voir rolldown.md pour les différences (ex : manualChunks objet supprimé au profit de codeSplitting.groups).
Vanilla SPA — point d'entrée index.html
<!-- index.html -->
<!doctype html>
<html lang="en">
<head>
<meta charset="UTF-8" />
<title>Vite App</title>
</head>
<body>
<div id="app"></div>
<script type="module" src="/src/main.ts"></script>
</body>
</html>Vite traite index.html comme un fichier source, pas un template statique : les balises <script type="module"> et les chemins relatifs sont résolus et transformés au build.
Library authoring — build.lib
// vite.config.ts
import { defineConfig } from 'vite';
import dts from 'vite-plugin-dts';
export default defineConfig({
plugins: [dts({ include: ['src'], rollupTypes: true })],
build: {
lib: {
entry: 'src/index.ts',
formats: ['es', 'cjs'],
},
rolldownOptions: {
external: ['some-peer-dependency'],
},
},
});Multi-page app — input (top-level)
// vite.config.ts
import { defineConfig } from 'vite';
import { resolve } from 'node:path';
export default defineConfig({
// top-level `input` (also used by the dev server); build.rolldownOptions.input overrides it for build only
input: {
main: resolve(__dirname, 'index.html'),
admin: resolve(__dirname, 'admin/index.html'),
},
});Workers / WASM
// Worker dédié (module worker, pattern supporté nativement par Vite)
const worker = new Worker(new URL('./worker.ts', import.meta.url), { type: 'module' });
// WASM (import direct, instancié via ?init)
import init, { compute } from './pkg/compute.wasm?init';
await init();
console.log(compute(42));Checklist Rapide
- Vite 8.3.x avec Rolldown (défaut) — pas de
manualChunksobjet - Project shape unique et non ambigu (vanilla SPA / library / MPA / workers-wasm)
- TypeScript strict mode +
vite-env.d.tsréférencé - Vitest >= 80% coverage, Browser Mode pour workers/WASM
- ESLint flat config (
eslint.config.js) vite-plugin-dtspour toute library —.d.tsvérifiés dansdist/- Aucun secret exposé via
envPrefix(VITE_*)
Documentation Complète
architecture.md— Les 4 project shapes, arborescences ASCIIcoding-standards.md— Conventionsvite.config.ts, nommagevite-plugin-*tooling.md— ESLint flat config,tsc --noEmit, scripts npmquality-tools.md— CI/CD, bundle analysis, pre-commit hookstesting.md— Vitest framework-agnostic (modules, plugins, workers/WASM)security.md—envPrefix,define(), CSP multi-page, sandboxing WASMrolldown.md— Migration esbuild → Rolldown (Vite 8)project-context.md— Template de contexte projet
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

