-
-
Notifications
You must be signed in to change notification settings - Fork 9.5k
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
[Bug]: Broken React 18 peer dependency when installing sb@next
having old(?) @storybook/blocks 7.0.0-alpha.8
with outdated @mdx-js/react version
#21396
Comments
Here in git on the next branch, storybook/code/ui/blocks/package.json Lines 2 to 3 in 3ea1a30
|
@storybook/blocks 7.0.0-alpha.8
@storybook/blocks 7.0.0-alpha.8
sb@next
via old(?) @storybook/blocks 7.0.0-alpha.8
with outdated @mdx-js/react version
sb@next
via old(?) @storybook/blocks 7.0.0-alpha.8
with outdated @mdx-js/react versionsb@next
having old(?) @storybook/blocks 7.0.0-alpha.8
with outdated @mdx-js/react version
Also after installing storybook, depreciated warning for _tooling/storybook | WARN deprecated stable@0.1.8 |
I suspect it might be a lockfile issue @D1no, try regenerating it? |
No, it's a fresh install. Also shows up in the (unrelated) storybook reproduction - |
Closing this, as with |
Describe the bug
Just installed the latest storybook 7 version in our
pnpm
monorepo, where react 18.2 is global and got the following. Not sure why@mdx-js/react
is at version1.6.22
in SB <-> while the latest release of mdx is2.3.0
at time of writing (?)To Reproduce
Using
pnpm@7.28.0
(latest stable) though this dependency problem is package manager unrelated.Strict Peer Dependencies
Create
.npmrc
file withstrict-peer-dependencies = true
Add React 18 to empty project
Init Storybook
Result during install
System
Additional context
In #20260 and #14119 it was said that mdx was updated in december (?)
The text was updated successfully, but these errors were encountered: