HeroUI Migration FAQs

Question 1

What kind of changes does HeroUI Migration help with?

Accepted Answer

It addresses various migration challenges, including changes to compound component APIs, package/import paths, updated overlay and hook patterns, and provides assistance for Tailwind/CSS workflow changes between v2 and v3.

Question 2

How does it help clarify component changes and documentation?

Accepted Answer

The tool generates a comprehensive documentation corpus for both v2 and v3, optimized for migration lookup. Its 'compare_component' feature helps distinguish between same, renamed, compound API, or removed components.

Question 3

What is the recommended workflow to use HeroUI Migration?

Accepted Answer

The recommended workflow involves verifying the documentation corpus, scanning your project to identify affected files, analyzing representative files, rewriting safe patterns, auditing your Tailwind configuration, and validating uncertain components, all while testing incrementally.

Question 4

What is HeroUI Migration?

Accepted Answer

HeroUI Migration is an MCP server designed to automate and assist the upgrade of HeroUI v2 and NextUI projects to HeroUI v3 beta. It uses project scanning, file analysis, guided rewrites, component comparison, and documentation lookup to streamline the process.

Question 5

Is the migration process fully automatic?

Accepted Answer

While HeroUI Migration automatically rewrites a subset of safe code patterns, it emphasizes a 'controlled, review-first workflow'. Manual review is still recommended for complex areas like navbar code, overlay logic, modal composition, and advanced Tailwind/theming patterns.

HeroUI Migration

HeroUI Migration

主要功能

使用案例

主要功能

使用案例