lately i was in the same spot with my team - we had built something on elasticsearch's ui library and it got us into some serious performance issues. 188kb ain't light, y'know? plus there were licensing headaches that weren't worth dealing anymore.
so yeah, migration time . but here's a heads up: the official docs won't save u this go around .
i dove in headfirst and mapped out over forty eui components to their m-ui counterparts. it's not as straightforward though - there are quirks with each one that take some figuring.
if u're gonna make t'this happen, i got a few tips:
-
start small : pick just 10 key features/components and get them working first.
> e. g, buttons & forms - super common stuff you'll need right awaypay attention to state management : it's different in each framework. make sure u understand how context or hooks work before diving deeper.
- use dev tools: browser developer consoles are ur best friend here . they can show ya where things go wrong faster than any documentation.
> plus, you get instant feedback on what changes affect the uiif anyone's got more tips from their own migrations - drop them below! we could all use a helping hand.
https://dev.to/ch-bas/migrating-from-elastic-eui-to-mui-chakra-or-ant-design-the-complete-playbook-3l2f