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
Is your feature request related to a problem? Please describe
Currently, one can provide an initial vite config in form of a config file. But some (meta) frameworks like nuxt don't have a config file but manage their vite config themselves (and usually provide functions to receive or modify the config). In order to make it easier to use these frameworks, it would be nice if there would be an viteInitial hook that one could use to provide the vite config from those frameworks, and then storybook goes on and modifies this config as it seems fit.
Describe the solution you'd like
Provide viteInitial (in analog to viteFinal) that can be used to provide the initial vite config.
Describe alternatives you've considered
One could use the viteFinal config to merge the storybook config with the frameworks config. However, then one needs to take care of the same things that storybook does under the hood. As an example, vue-vite vue plugin but vue frameworks have their own manually configured vue plugin. So one needs to decide which one to use.
Are you able to assist to bring the feature to reality?
no
Additional context
No response
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem? Please describe
Currently, one can provide an initial vite config in form of a config file. But some (meta) frameworks like nuxt don't have a config file but manage their vite config themselves (and usually provide functions to receive or modify the config). In order to make it easier to use these frameworks, it would be nice if there would be an
viteInitial
hook that one could use to provide the vite config from those frameworks, and then storybook goes on and modifies this config as it seems fit.Describe the solution you'd like
Provide
viteInitial
(in analog toviteFinal
) that can be used to provide the initial vite config.Describe alternatives you've considered
One could use the
viteFinal
config to merge the storybook config with the frameworks config. However, then one needs to take care of the same things that storybook does under the hood. As an example,vue-vite
vue plugin but vue frameworks have their own manually configured vue plugin. So one needs to decide which one to use.Are you able to assist to bring the feature to reality?
no
Additional context
No response
The text was updated successfully, but these errors were encountered: