We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
When I run 2 storybooks locally (main on 6006 and composition storybook on 7007) I get this error:
Can this be solved with a setting or is this a bug in storybook itself?
No response
Storybook Environment Info: System: OS: Windows 11 10.0.22631 CPU: (12) x64 Intel(R) Core(TM) i7-10750H CPU @ 2.60GHz Binaries: Node: 20.11.1 - C:\Program Files\nodejs\node.EXE Yarn: 1.22.21 - C:\Program Files\nodejs\yarn.CMD npm: 10.2.4 - C:\Program Files\nodejs\npm.CMD <----- active pnpm: 8.15.1 - C:\Program Files\nodejs\pnpm.CMD Browsers: Edge: Chromium (122.0.2365.66) npmPackages: @storybook/addon-essentials: 8.0.0-rc.3 => 8.0.0-rc.3 @storybook/addon-links: 8.0.0-rc.3 => 8.0.0-rc.3 @storybook/addon-themes: 8.0.0-rc.3 => 8.0.0-rc.3 @storybook/blocks: 8.0.0-rc.3 => 8.0.0-rc.3 @storybook/manager-api: 8.0.0-rc.3 => 8.0.0-rc.3 @storybook/theming: 8.0.0-rc.3 => 8.0.0-rc.3 @storybook/vue3: 8.0.0-rc.3 => 8.0.0-rc.3 @storybook/vue3-vite: 8.0.0-rc.3 => 8.0.0-rc.3 eslint-plugin-storybook: 0.8.0 => 0.8.0 storybook: 8.0.0-rc.3 => 8.0.0-rc.3
The text was updated successfully, but these errors were encountered:
@ndelangen I guess this isn't related to #26288, is it?
Sorry, something went wrong.
@DotwoodMedia was it working as expected in v7? and have both storybooks been upgraded to v8?
I can take a look if you have a reproduction to share @DotwoodMedia
The composition works again since 8.0.0-rc.4. Turned out to be the same problem as #26288
No branches or pull requests
Describe the bug
When I run 2 storybooks locally (main on 6006 and composition storybook on 7007) I get this error:
Can this be solved with a setting or is this a bug in storybook itself?
To Reproduce
No response
System
Additional context
No response
The text was updated successfully, but these errors were encountered: