Closed kontibosun closed 1 year ago
Ran into this a bit ago, needed to return config
from the viteFinal
function
Ah, yes that is most likely the cause, thanks for sharing, @Jack-Barry.
@kontibosun Please let us know if that doesn't solve your issue.
Ran into this a bit ago, needed to return
config
from theviteFinal
function
OMG this worked! Thanks man!
What version of
vite
are you using?4.0.0
System info and storybook versions
System: OS: macOS 13.0 CPU: (8) arm64 Apple M2 Binaries: Node: 16.19.0 - ~/.nvm/versions/node/v16.19.0/bin/node Yarn: 1.22.19 - /usr/local/bin/yarn npm: 8.19.3 - ~/.nvm/versions/node/v16.19.0/bin/npm Browsers: Chrome: 110.0.5481.177 Safari: 16.1 npmPackages: @storybook/addon-actions: ^6.5.16 => 6.5.16 @storybook/addon-essentials: ^6.5.16 => 6.5.16 @storybook/addon-interactions: ^6.5.16 => 6.5.16 @storybook/addon-links: ^6.5.16 => 6.5.16 @storybook/builder-vite: ^0.4.2 => 0.4.2 @storybook/testing-library: ^0.0.13 => 0.0.13 @storybook/vue3: ^6.5.16 => 6.5.16
Describe the Bug
Tried to run the storybook
yarn storybook
Following occured:
Tried removing
node_modules
and didnpm i
also tried withyarn install
. All same results, no luck.Following is my
main.js
file:I noticed if I comment out
async viteFinal()
, it will work.Link to Minimal Reproducible Example
No response
Participation