-
-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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
@types/react conflict for @types/[email protected] #2167
Comments
We do not depend on the exact version of Please always try to share a repro case in a runnable form - either by providing a git repository to clone or a codesandbox. OSS maintainers usually can't afford the time to set up the repro, even if exact steps are given. |
Back to the drawing board. I'm unsure where this is coming from. Perhaps it's because there was a change from I'm hoping this is where the conflict is coming from. Hopefully it's solved by this: storybookjs/storybook#13300 |
There is also this issue with Storybook: storybookjs/storybook#13145 . I believe this should be fixed as well - they shouldn't enforce a single version of Emotion packages like that because they don't control what their users actually use. That being said - not sure if this is going to resolve your issue anyway. If you provide a repro case I could take a look at it. |
Closing this stale issue because there doesn't seem to be anything actionable for our team. Seems like the conflict may originate from Storybook rather than Emotion. |
Current behavior:
There's a conflict between
@types/react
and@emotion/react
– likely because@emotion/react
is using the@types/[email protected]
vs the more recent@types/[email protected]
:Environment information:
react
version: 17.0.1@types/react
: 17.0.0@emotion/react
version: 11.1.2The text was updated successfully, but these errors were encountered: