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
storybook add @storybook/experimental-addon-vitest
1: Install dependency and register the addon to main.js
2.1: User does not have any vite dependency/config and is not using Nextjs
2.2: User does not have any vite dependency/config and is using Nextjs
vite
vite-plugin-storybook-nextjs
2.3: User does have Vitest and not workspaces
2.4: User does have Vite but not Vitest
vitest
@vitest/browser
playwright
npx playwright install
storybook.setup.ts
vitest.config.ts
viteFinal
vite.config.ts
resolve: { alias: { vue: 'vue/dist/vue.esm-bundler.js', }, },
2.5: User does have Vite and Vitest
The text was updated successfully, but these errors were encountered:
kasperpeulen
Successfully merging a pull request may close this issue.
Command:
Behavior of the command:
1: Install dependency and register the addon to main.js
2.1: User does not have any vite dependency/config and is not using Nextjs
2.2: User does not have any vite dependency/config and is using Nextjs
vite
vite-plugin-storybook-nextjs
plugin and point to its docs: https://storybook.js.org/docs/get-started/frameworks/nextjs#with-vite2.3: User does have Vitest and not workspaces
2.4: User does have Vite but not Vitest
vitest
,@vitest/browser
andplaywright
npx playwright install
(chromium)storybook.setup.ts
andvitest.config.ts
vitest.config.ts
viteFinal
in main.js, warn them about using that config in the vite filevite.config.ts
if that file exists (nextjs probably won't have it)vite-plugin-storybook-nextjs
if applicableresolve: { alias: { vue: 'vue/dist/vue.esm-bundler.js', }, },
2.5: User does have Vite and Vitest
The text was updated successfully, but these errors were encountered: