React 18 - Chakra UI v2
See original GitHub issueWe are starting the development of Chakra UI v2 🎉
The scope of this upcoming major release is to support React 18 and remove long known deprecations. We keep the scope as narrow as possible to provide feature-scoped major releases to all our users and a smooth upgrade experience.
We switched our default branch from main
to next
. This allows us to publish the pre-release version á la @chakra-ui/react@2.0.0-next.X
. The first next release was published moments ago.
With this in place, we can test the React 18 support in our applications and resolve upcoming issues until we are confident to release Chakra UI v2.
If you experience any React 18 related issues or tips we should know about, feel free to comment below and we’ll look into it.
Upgrade guide
- Update
react
,react-dom
and their respective@types/
package to version 18 - Upgrade to the
next
pre-release - Test and report any issues you have below.
Join our Discord Server for React 18 issues: https://discord.gg/kfp3UQh4Y2
Issue Analytics
- State:
- Created a year ago
- Reactions:214
- Comments:50 (19 by maintainers)
Top GitHub Comments
We just released version
@chakra-ui/react@2.0.0
🎉It’s the https://chakra-ui.com/ website for the latest version of Chakra UI. You can find our Migration Guide to v2 here: https://chakra-ui.com/guides/migration
For our v1 docs head over here https://v1.chakra-ui.com/
I had the same issue with modals. When I updated framer-motion to 6.3.0, the problem was solved