-
Notifications
You must be signed in to change notification settings - Fork 47
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conflicting @emotion/react #141
Comments
What's the version difference? maybe we can upgrade to the latest if that's the issue, but it's a devtool so it's not bundle into your prod code, so i wouldn't worry too much about it. |
Mantine v5 currently uses @emotion/react version 11.9.3. As DevTools is often used with other component UI libraries (and Emotion is a very common style library) wouldn't it make sense to declare Emotion as a peer dependency in DevTools? But maybe you are right, and I should just ignore the warnings. |
I think it's fine to ignore. |
Yes, I will ignore it. But there are also some discussions in the Emotion repo itself if emotion-js/emotion#2343 (comment) Even Mantine seems to switch mantinedev/mantine#1715 |
oh i see, would you like to send a PR to adjust that? happy to re-release if that will resolve the issue. |
Sure, it is as easy as moving the dependency line to peer dependencies. As version restriction, I would use |
Fixes Conflicting @emotion/react react-hook-form#141
Fixes Conflicting @emotion/react #141
this caused issue: https://codesandbox.io/s/react-hook-form-get-started-ts-forked-o1ebc5?file=/src/index.tsx Will revert that commit for now. |
Sure, I will investigate what's wrong here. Sorry for the trouble. |
not at all, thanks for contributing and helping. 🙏 |
I took another look into this. This import is a bit strange: Also, there is no |
oops, you are right... was using a CSB reference to src folder i will revert (revert) your merge |
never mind, it's already released, I didn't revert your original commit. could you verify it's working? |
It seems reverted as |
oops, would like you to push your PR again? let's remerge it? |
My app uses Mantine component library, which uses Emotion under the hood. But it seems React Hook Form DevTools also uses Emotion, but a different version. When I add DevTools to my app, I now get the following warning on the console:
You are loading @emotion/react when it is already loaded. Running multiple instances may cause problems. This can happen if multiple versions are used, or if multiple builds of the same version are used.
Should I ignore it, or is there a way to make DevTools more "sandboxed"?
The text was updated successfully, but these errors were encountered: