Replies: 3 comments 2 replies
-
|
I came here to say exactly this. We have a quite large production React app for our business, and migrating the entire thing at once is impossible. We have a much smaller internal app that uses Chakra as well that I've begun playing with. I tested out running v2 and v3 side by side. See code example below. This feels like it would allow gradual migration for different teams to opt-in to adopting v3 and fixing the bugs they find along the way in small incremental pieces. I agree there are tons of small things that pop up as you go which are not covered in the migration guide, and AFAICT there are no codemods to assist. @segunadebayo do you see any risks with this approach? Package.json "@chakra-ui/react": "2.8.2",
"@chakra-ui/react-v3": "npm:@chakra-ui/[email protected]",
"@emotion/react": "^11.14.0",
"@emotion/styled": "^11.14.0",Root Layout const MainLayout = ({ children }: PropsWithChildren<{}>): JSX.Element => {
return (
<ChakraProvider theme={extendTheme(customTheme)} resetCSS={true}>
<ChakraProviderV3 value={customSystem}>
<Flex flex={1}>{children}</Flex>
</ChakraProviderV3>
</ChakraProvider>
)
}Opt-in components import { Box, Button, ButtonProps, HStack, Text } from '@chakra-ui/react-v3'
... |
Beta Was this translation helpful? Give feedback.
-
|
I also have a similar problem to yours @jamesopti - our application is big, it's nearly impossible to migrate it all at once, so I'd also wanted to try to do it incrementally. My idea is to build a separate UI library based on Chakra v3 and keep on exchanging component by component in the main app whenever we have time (the separate library would also help us in the future, when breaking changes hit again). I have all setup ready and working (JSRepo + Yalc). I mean, almost working - I solved all versioning and build problems and again, I came back to Chakra guts issues - when I use two chakra Providers, like in the above example, components from Chakra v2 work perfectly fine, but the ones from v3 don't - they come with no styles at all. In general, when I comment out Chakra v2 provider, then v3 styles start working. If anyone has a solution to this problem, please let me know. I guess the problem may be overriding components in v3 with v2 config, maybe somewhere in the provider, they |
Beta Was this translation helpful? Give feedback.
-
|
@segunadebayo Do you have any thoughts on this? |
Beta Was this translation helpful? Give feedback.
-
|
We have the same problem... It's easier migrate from Chakra v2 to shadcn than v3 |
Beta Was this translation helpful? Give feedback.
-
|
We decided to migrate to MUI because it supports gradual adoption, making the transition to a newer version more manageable. While there are both pros and cons, MUI stands out as a mature and well-established UI library. |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
Hello, is there a way to gradually migrate from V2 to V3? We're facing a tremendous amount of work, along with numerous hidden issues that aren't covered in the migration documentation but are only discovered along the way.
Beta Was this translation helpful? Give feedback.
All reactions