3 ms·
MUI v5 absolutely supported React 17 though. Unless you're thinking of React 16, which hadn't had updates for almost a year when MUI v5 released.
by c-hendricks 3mo ago
MUI v5 absolutely supported React 17 though. Unless you're thinking of React 16, which hadn't had updates for almost a year when MUI v5 released.
- slowjames 3mo agoOh yes you are right. My bad. I got my dependencies backwards. We were using react 17 and wanted to upgrade to 18, but first we had to migrate an entire app on MUI v4 to v5 first since v4 was not supported by 18. And it was an upgrade full of breaking changes. My point still stands that having a UI library like MUI deeply ingrained into your app can cause dependency and other issues like this. The speed you get upfront can bite you if you don’t plan carefully. Sure there are steps we could have taken to avoid such a mess. But that’s not how things often work out.
- c-hendricks 3mo agoStill not sure if the alternative of vendoring like Shadcn, where a migration like this requires a black box probability machine to do the migration for you is any better.
- slowjames 3mo agoMy understanding is they made an LLM skill for updating because it’s trendy and people are gonna point an agent at it anyway. I think the winning idea is you can update components in your design system piecemeal instead of needing to do a Migration.