vue-patterns

To check Vue 3 projects for Composition API anti-patterns, validate the codebase against modern standards enforcing script setup, typed props, and correct reactive primitives. This generates a measurable compliance report identifying legacy patterns and missing TypeScript typings.

Common Vue 3 anti-patterns include using the Options API instead of script setup, missing keys in component templates, and avoiding typed props. Replacing Vuex with Pinia stores for global state management is required to meet type-safe state management standards.

Vue 3 patterns validation does not work with legacy Vuex state management. It requires Pinia stores for global state management to enforce type-safe code, actively discouraging Vuex to ensure compliance with modern Composition API and TypeScript standards.

Enforce typed props and script setup in a Vue 3 codebase by applying fitness criteria that require 100% typed props and TypeScript typings. This evaluates component templates and reactive primitives to produce a patterns compliance checklist.

Validate reactive primitives in Vue 3 components when using ref, reactive, computed, and watch to ensure type-safe code. Applying validation rules detects incorrect usage and anti-patterns, guaranteeing adherence to modern Composition API guidelines.

The best way to migrate a Vue 3 project to script setup and Pinia is to scan the codebase against fitness criteria. This identifies legacy anti-patterns, missing TypeScript typings, and Vuex usage, providing a compliance report for clean, type-safe code.