Component Migration Strategy with Chakra UI

[Dishant1804]

With respect to the migrations and standardizing the components by using ChakraUI Library, We would like suggestions from the community. I am considering the following options :

• OPTION 1 : Implementing Emotion CSS as a complete replacement for Tailwind CSS alongside Chakra UI
• OPTION 2 : Adopting a hybrid approach where Emotion CSS is utilized only when necessary for Chakra UI component recipes, while maintaining Tailwind CSS for the rest of the codebase

In my opinion, the 2nd option looks better and aligns with our codebase

Why This approach

This hybrid implementation would minimize refactoring overhead while still enabling us to standardize the components. It also provides a clearer migration path that can be executed incrementally without disrupting current development workflows.

Let me know your thoughts, Lets discuss and arrive to the solution that the community collectively needs :)

[KaranNegi20Feb]

Well I agree with the hybrid approach because by retaining Tailwind for existing code, we can avoid a massive rewrite, which can be time-consuming and risky.

[Rajgupta36]

Agree with option 2. I think Tailwind has a broader scope, so instead of removing it, we can add Emotion CSS to the components where needed.