❓ Type of change

Resolves #2828, resolves #3290, resolves https://github.com/nuxt/ui-pro/issues/718

• 📖 Documentation (updates to the documentation or readme)
• 🐞 Bug fix (a non-breaking change that fixes an issue)
• 👌 Enhancement (improving an existing functionality)
• ✨ New feature (a non-breaking change that adds functionality)
• 🧹 Chore (updates to the build process or auxiliary tools and libraries)
• ⚠️ Breaking change (fix or feature that would cause existing functionality to change)

📚 Description

This PR refactors how component types are handled following the @nuxt/module-builder upgrade to keep dynamic props autocomplete based on user's app.config.ts and generated theme (based on options https://ui.nuxt.com/getting-started/installation/pro/nuxt#themecolors).

Check this failed CI on nuxt.com after using @nuxt/ui after the upgrade: https://github.com/nuxt/nuxt.com/actions/runs/14356582555/job/40247328611?pr=1853

Also, the tailwind-variants computation based on #build/app.config that used to be done inside normal script has been moved to setup script which makes components dynamic when app.config.ts changes through HMR. I hope this will not degrade performances which was why this was done in normal script initially.

📝 Checklist

• I have linked an issue or discussion.
• I have updated the documentation accordingly.