-
-
Notifications
You must be signed in to change notification settings - Fork 9.6k
Open
Labels
Description
Describe the bug
We recently upgraded to Storybook v7 and now some of our team are struggling to run the updated version of Storybook.
We previously had this same issue in v6, however the fix stated in this thread Issue19336 worked for us until now with the upgrade to v7 :(
To Reproduce
Run npm run storybook after upgrading to v7
System
Environment Info:
System:
OS: Windows 10 10.0.22621
CPU: (20) x64 12th Gen Intel(R) Core(TM) i9-12900H
Binaries:
Node: 18.16.0 - C:\Program Files\nodejs\node.EXE
npm: 9.5.1 - C:\Program Files\nodejs\npm.CMD
Browsers:
Edge: Spartan (44.22621.1848.0), Chromium (114.0.1823.51)
npmPackages:
@storybook/addon-a11y: ^7.0.21 => 7.0.21
@storybook/addon-actions: ^7.0.21 => 7.0.21
@storybook/addon-console: ^2.0.0 => 2.0.0
@storybook/addon-docs: ^7.0.21 => 7.0.21
@storybook/addon-essentials: ^7.0.21 => 7.0.21
@storybook/addon-interactions: ^7.0.21 => 7.0.21
@storybook/addon-links: ^7.0.21 => 7.0.21
@storybook/addon-mdx-gfm: ^7.0.21 => 7.0.21
@storybook/addons: ^7.0.21 => 7.0.21
@storybook/mdx1-csf: ^1.0.0 => 1.0.0
@storybook/node-logger: ^7.0.21 => 7.0.21
@storybook/preset-create-react-app: ^7.0.21 => 7.0.21
@storybook/react: ^7.0.21 => 7.0.21
@storybook/react-webpack5: ^7.0.21 => 7.0.21
@storybook/testing-library: ^0.1.0 => 0.1.0
@storybook/theming: ^7.0.21 => 7.0.21
Additional context
rw-yehormalchenko