check-nuxt-ui-v4

To migrate Nuxt UI v3 components to v4, scan your Markdown documents to detect v3 syntax patterns and apply automated replacements. This process identifies specific component names and attributes, returning structured results with suggested v4 updates for consistent styling.

Common Nuxt UI v3 patterns requiring migration include updating UFormGroup to UFormField, replacing the :options or v-bind:options attribute with :items, and migrating UButtonGroup syntax. Pattern detection scans for these specific syntaxes to provide structured replacement guidance.

Yes, you can automatically detect and fix Nuxt UI v3 syntax in markdown files. The automated pattern detection scans documents under directories like docs/working, flags outdated v3 component names and attributes, and provides suggested v4 replacements for consistent documentation styling.

The Nuxt UI v4 migration check is applicable to markdown sources within your project, specifically targeting documentation under docs/working. It scans these markdown documents to identify v3 component patterns and returns structured migration guidance for v4 compatibility.

The best way to update UFormGroup and options attributes for Nuxt UI v4 is using automated pattern detection. It identifies UFormGroup for replacement with UFormField, flags :options attributes for conversion to :items, and returns structured results with suggested replacements across your documentation.

Nuxt UI documentation still shows v3 component patterns after upgrading because markdown files require separate migration checks. Scanning documents under docs/working detects outdated syntax like UFormGroup and :options attributes, providing structured results with suggested v4 replacements to fix inconsistencies.