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
Duplicate of #23816
I am seeing this in the browser console locally when I do npx storybook@latest init in an empty directory and choose the react-vite-ts template.
npx storybook@latest init
react-vite-ts
Interestingly, I do not see this in the linked stackblitz repro 😵
https://stackblitz.com/edit/github-2nczml
No response
Storybook Environment Info: System: OS: macOS 14.4.1 CPU: (10) arm64 Apple M1 Pro Shell: 5.9 - /bin/zsh Binaries: Node: 18.19.0 - /usr/local/bin/node Yarn: 1.22.21 - /usr/local/bin/yarn npm: 10.2.3 - /usr/local/bin/npm <----- active pnpm: 9.0.6 - ~/Library/pnpm/pnpm Browsers: Chrome: 124.0.6367.208 Safari: 17.4.1 npmPackages: @storybook/addon-essentials: ^8.1.1 => 8.1.1 @storybook/addon-interactions: ^8.1.1 => 8.1.1 @storybook/addon-links: ^8.1.1 => 8.1.1 @storybook/addon-onboarding: ^8.1.1 => 8.1.1 @storybook/addon-styling-webpack: ^1.0.0 => 1.0.0 @storybook/blocks: ^8.1.1 => 8.1.1 @storybook/nextjs: ^8.1.1 => 8.1.1 @storybook/react: ^8.1.1 => 8.1.1 @storybook/test: ^8.1.1 => 8.1.1 storybook: ^8.1.1 => 8.1.1
### Additional context _No response_
The text was updated successfully, but these errors were encountered:
Here's another one that's near and dear to our hearts @valentinpalkovic @vanessayuenn
Sorry, something went wrong.
No branches or pull requests
Describe the bug
Duplicate of #23816
I am seeing this in the browser console locally when I do
npx storybook@latest init
in an empty directory and choose thereact-vite-ts
template.Interestingly, I do not see this in the linked stackblitz repro 😵
Reproduction link
https://stackblitz.com/edit/github-2nczml
Reproduction steps
No response
System
The text was updated successfully, but these errors were encountered: