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
docs page dose not show story source code with vite builder. It shows "No code avaliable". Storybook version: 7.0.0-alpha.40
npm init vue@latest cd <your-project-name> npm install npx storybook init@next
No response
Environment Info: System: OS: macOS 12.5.1 CPU: (12) x64 Intel(R) Core(TM) i7-9750H CPU @ 2.60GHz Binaries: Node: 14.20.1 - ~/.nvm/versions/node/v14.20.1/bin/node Yarn: 1.22.19 - ~/.nvm/versions/node/v14.20.1/bin/yarn npm: 6.14.17 - ~/.nvm/versions/node/v14.20.1/bin/npm Browsers: Chrome: 106.0.5249.119 Firefox: 105.0 Safari: 15.6.1 npmPackages: @storybook/addon-essentials: ^7.0.0-alpha.40 => 7.0.0-alpha.40 @storybook/addon-interactions: ^7.0.0-alpha.40 => 7.0.0-alpha.40 @storybook/addon-links: ^7.0.0-alpha.40 => 7.0.0-alpha.40 @storybook/testing-library: ^0.0.13 => 0.0.13 @storybook/vue3: ^7.0.0-alpha.40 => 7.0.0-alpha.40 @storybook/vue3-vite: ^7.0.0-alpha.40 => 7.0.0-alpha.40
The text was updated successfully, but these errors were encountered:
related storybookjs/builder-vite#111
Sorry, something went wrong.
Jiminy cricket!! I just released https://github.com/storybookjs/storybook/releases/tag/v7.0.0-beta.0 containing PR #20147 that references this issue. Upgrade today to the @next NPM tag to try it out!
@next
npx sb upgrade --prerelease
Closing this issue. Please re-open if you think there's still more to do.
No branches or pull requests
Describe the bug
docs page dose not show story source code with vite builder. It shows "No code avaliable".
Storybook version: 7.0.0-alpha.40
Reproduce
To Reproduce
No response
System
Additional context
No response
The text was updated successfully, but these errors were encountered: