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
[Storybook 6.4] [Vue] [addon-docs] Stories are hidden in docs tab #16798
Comments
I found that the Docs tab last worked for Vue in Edit: In fact, will take a stab and say it's this particular change that is involved: 83f223e#diff-850e2e1559576ae7e040a8fb199b86c3d75c0da9dbd0c7368b913cd38c762386R4 |
Actually, that leads me to a potential workaround for .storybook/preview-head.html
|
The problem also occurs in the kitchen-sink: https://next--storybookjs.netlify.app/vue-kitchen-sink/?path=/docs/button--rounded |
The workaround from @spiltcoffee works for me, but only in the canvas tab, the Doc tab is still hidden. I see that storybook seems to add an error overlay, but actutally no errors occured for my components. I'm using storybook with React. This fixed both tabs for me:
|
Same issue here! @spiltcoffee workaround works 👍 |
So the "root" of this issue (zing) is that the
That's clearly invalid (can't have >1 element with the same |
Ooh-la-la!! I just released https://github.com/storybookjs/storybook/releases/tag/v6.4.3 containing PR #16850 that references this issue. Upgrade today to the
Closing this issue. Please re-open if you think there's still more to do. |
Describe the bug
After updating to storybook-6.4.0-rc.11 in a vue-2 project, the CSF stories in the docs tab are rendered, but hidden by
For MDX stories there is a warning in the console and the element is only rendered partially(?)
To Reproduce
An example can be found here: https://github.com/bodograumann/vue-cli-plugin-storybook/tree/webpack-5
To seethe error:
System
Additional context
The problem was initially brought up on the discord support channel by someone else.
With vue-3 everything seems to work fine.
The text was updated successfully, but these errors were encountered: