Migration tool/guide from daisyUI

[kuchta]

It would be very handy to have some migration tool or guide how to upgrade project from daisyUI to FlyonUI.

[yagnikvamja]

Hello @kuchta ,

Thank you for your interest in FlyonUI! While we don’t currently offer a dedicated migration tool or guide for transitioning from daisyUI, we’re happy to provide some general recommendations to assist with the process.

FlyonUI is designed as a standalone library rather than a direct drop-in replacement for daisyUI, so some components and class structures may differ. Here’s how you can approach the migration effectively:

• Identify the daisyUI components in use – Start by listing all the daisyUI components currently integrated into your project.

• Refer to FlyonUI’s documentation – Review our component library to find and replace equivalent JS components for interactive elements like Accordion, Dropdown, Modal, Collapse, etc.

• Incremental replacement – Instead of a complete overhaul, consider replacing components in stages to ensure smooth integration and minimal disruptions.

Pay attention to class names and structure – FlyonUI follows a distinct naming convention, so adjustments may be required when replacing components. For example, the toggle component in daisyUI is referred to as switch in FlyonUI, also chat-bubble structure is different.

[kuchta]

Thank you, @yagnikvamja . I still think that creating some codemon would bring a lot of potential users currently using daisyUI, for whom the css-only nature of daisyui is no longer enough since daisyUI has arguably much-much larger users base, but at least some tool that would point out potential issues would probably help a lot 🙏🏻