This repository was archived by the owner on Jun 28, 2025. It is now read-only.
Make using automatically vite.config.js config optional. #564
yodakaEngineer
started this conversation in
Ideas
Replies: 2 comments 4 replies
-
|
Would it meet your needs to create another, simpler vite config file and point storybook at that? |
Beta Was this translation helpful? Give feedback.
3 replies
-
|
For me vite-ruby caused storybook to try loading assets from port 3036 instead of 6006. Here's how I exclude it for storybook: In import { Plugin } from 'vite';
viteFinal: async (config) => {
config.plugins = config.plugins?.flat()?.filter((p) => !~(p as Plugin).name.indexOf('vite-plugin-ruby'));
return config;
}, |
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
In v7, Storybook use vite.config.(ctm)js config automatically.
https://github.com/storybookjs/storybook/blob/next/MIGRATION.md#vite-builder-uses-vite-config-automatically
I use ViteRuby for build application code and server for dev.
But I don't want to use it for storybook because its too much for storybook.
So I want to disable automatically using vite.config.js.
Beta Was this translation helpful? Give feedback.
All reactions