claude-craft / vuejs
CLAUDE.md108 starsChanged 5 days agoMITView on GitHub
Source : Vue 3.6 Vapor blog | Vite 8 Pinia 2 → 3 : l'API defineStore reste compatible ; la migration principale concerne la suppression des mapState/mapActions dans les Options API. Préférer le setup store style (ci-dessus) en Pinia 3. Pinia 3 → 4 : uniquement des breaking changes techniques — Pinia 4 est ESM-only et @vue/devtools-api (v8) doit être installé explicitement à côté de pinia (npm i pinia @vue/devtools-api). Source : https://github.com/vuejs/pinia/releases Vite 8 / Rolldown (défaut) : la…
- Installs packages
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/vite/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
Vue.js 3.5+ / 3.6 RC Vapor - Quick Reference
Versions Requises (2026)
| Composant | Version | Notes |
| Vue.js | 3.5.x (stable) / 3.6.x RC (rc.14) | Vapor Mode : feature-complete, instable (hydratation SSR en cours de stabilisation) |
| Pinia | 4.x | ESM-only ; @vue/devtools-api v8 à installer explicitement ; 3+ requis pour Vapor Mode |
| Vue Router | 5.x | File-based routing via @vue-router/auto |
| Vite | 8.x | Rolldown bundler par défaut (3-5× plus rapide) |
| TypeScript | 5.x+ | Strict mode obligatoire |
Source : Vue 3.6 Vapor blog | Vite 8
Architecture Composition API
src/
├── assets/ # Static assets
├── components/ # Composants partagés (base/, layout/, ui/)
├── composables/ # Fonctions réutilisables (use*)
├── modules/ # Feature modules (domain-driven)
│ └── [feature]/
│ ├── components/
│ ├── composables/
│ ├── stores/
│ ├── views/
│ └── types/
├── router/ # Vue Router config
├── stores/ # Stores Pinia globaux
├── services/ # Services API
├── types/ # Types TypeScript globaux
├── App.vue
└── main.tsPoints clés 2026
Composition API + <script setup> (obligatoire)
<script setup lang="ts">
import { ref, computed } from 'vue';
import { useUsersStore } from '@/modules/users/stores/users.store';
const store = useUsersStore();
const search = ref('');
const filtered = computed(() => store.users.filter(u => u.name.includes(search.value)));
</script>Pinia 4 (store composition style)
// stores/users.store.ts
import { defineStore } from 'pinia';
import { ref, computed } from 'vue';
export const useUsersStore = defineStore('users', () => {
const users = ref<User[]>([]);
const loading = ref(false);
const activeUsers = computed(() => users.value.filter(u => u.active));
async function fetchUsers() {
loading.value = true;
users.value = await api.getUsers();
loading.value = false;
}
return { users, loading, activeUsers, fetchUsers };
});Pinia 2 → 3 : l'API
defineStorereste compatible ; la migration principale concerne la suppression desmapState/mapActionsdans les Options API. Préférer le setup store style (ci-dessus) en Pinia 3.Pinia 3 → 4 : uniquement des breaking changes techniques — Pinia 4 est ESM-only et
@vue/devtools-api(v8) doit être installé explicitement à côté depinia(npm i pinia @vue/devtools-api). Source : https://github.com/vuejs/pinia/releases
Vite 8 — Rolldown
// vite.config.ts
import { defineConfig } from 'vite';
import Vue from '@vitejs/plugin-vue';
export default defineConfig({
plugins: [Vue()],
// Vite 8 / Rolldown (default): object form of manualChunks removed — use codeSplitting.groups
build: {
rolldownOptions: {
output: {
codeSplitting: {
groups: [
{ name: 'vue-vendor', test: /node_modules\/(vue|pinia|vue-router)/ },
],
},
},
},
},
});Vite 8 / Rolldown (défaut) : la forme objet de
manualChunksest supprimée (non supportée) ; la forme fonction est dépréciée. Utiliserbuild.rolldownOptions.output.codeSplitting.groups. Vite 7 / Rolldown désactivé (legacy) :build: { rollupOptions: { output: { manualChunks: { 'vue-vendor': ['vue', 'vue-router', 'pinia'] } } } } // Only if Rolldown is explicitly disabled
Vue Router 5 — File-Based Routing
// vite.config.ts — file-based routing (optionnel)
import VueRouter from 'unplugin-vue-router/vite';
export default defineConfig({
plugins: [
VueRouter({ routesFolder: 'src/pages' }), // avant Vue()
Vue(),
],
});Structure src/pages/ → routes auto-générées avec types précis. Pour un router manuel classique, configurer dans src/router/index.ts (voir architecture.md).
Alien Signals (Vue 3.5+)
Vue 3.5 migre en interne vers Alien Signals pour la réactivité : performances +2× sur les graphes larges. Aucun changement d'API côté utilisateur.
Vapor Mode (Vue 3.6 RC — ne pas utiliser en prod sans validation)
- Feature-complete mais instable — hydratation SSR Vapor en cours de stabilisation (rc.14), statut stable non confirmé
- Nécessite Pinia 3+ (4 recommandé) et
@vue-router/auto - Voir
vapor-mode.mdpour les détails et caveats
Checklist Rapide
- Vue 3.5.x stable (3.6 réservé expérimental)
- Composition API +
<script setup>uniquement - Pinia 4 setup store style
- Vue Router 5 (file-based ou manuel selon besoin)
- Vite 8 + Rolldown (
manualChunkssupprimé → migrer versrolldownOptions.output.codeSplitting.groups) - TypeScript strict mode
- Tests >= 80% coverage (Vitest)
- ESLint +
@vue/eslint-plugin-vue
Documentation Complète
architecture.md— Structure modulaire, patterns composables, routingcoding-standards.md— TypeScript, conventions, Composition API rulestooling.md— Vite 8, Vue Router 5, Pinia 4, migrationsquality-tools.md— ESLint, Vitest, audit qualitétesting.md— Vitest, Vue Test Utils, stratégies TDDsecurity.md— XSS, CSRF, validation, CSPvapor-mode.md— Vue 3.6 Vapor (expérimental)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.

