You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I am working in a vite monorepo which has to have set the NODE_ENV variable to 'production' by default. My storybook is running on the "@storybook/html-vite" framework. I manage to override the 'development' mode using 'viteFinal' in my SB config file when building storybook, but not when serving it via the CLI command 'storybook dev' , which triggers the vite.config.ts build function 'defineConfig' always in 'development' mode and does not wait for 'viteFinal' to complete.
Seems that vite.config.ts gets called before the viteFinal function in .storybook/main.ts.
Any ideas of how to bypass the default configuration mode 'storybook dev'. Thank you
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
I am working in a vite monorepo which has to have set the NODE_ENV variable to 'production' by default. My storybook is running on the "@storybook/html-vite" framework. I manage to override the 'development' mode using 'viteFinal' in my SB config file when building storybook, but not when serving it via the CLI command 'storybook dev' , which triggers the vite.config.ts build function 'defineConfig' always in 'development' mode and does not wait for 'viteFinal' to complete.
Seems that vite.config.ts gets called before the viteFinal function in .storybook/main.ts.
Any ideas of how to bypass the default configuration mode 'storybook dev'. Thank you
Beta Was this translation helpful? Give feedback.
All reactions