search

storybook-vue / storybook-nuxt

Deprecated in favor of https://github.com/nuxt-modules/storybook/
https://github.com/nuxt-modules/storybook/
134 stars 20 forks source link

Compatibility issues with Nuxt 3.7.x #75

Open pixleight opened 11 months ago

pixleight commented 11 months ago

I've been running into issues integrating Storybook with a newer Nuxt project, currently on 3.7.0, but I've seen the same issues with newer patch versions of 3.7

Most often, the errors seem related to Storybook being unable to connect to the Nuxt instance: [nuxt] instance unavailable

Steps to reproduce

  1. Run demo project at https://stackblitz.com/edit/github-dxsw3r
  2. In Storybook, navigate to NuxtLink/Docs and NuxtWelcome/Docs
    • NuxtLink uses the built-in <NuxtLink /> component, but shows an error [nuxt] instance unavailable
    • NuxtWelcome should render the built-in <NuxtWelcome /> component, but shows an error Identifier '_createElementVNode' has already been declared

Compare to the same demo project running Nuxt 3.6.5, which seems to work as expected: https://stackblitz.com/edit/github-dxsw3r-tjesvx

chakAs3 commented 11 months ago

please refer to https://storybook.nuxtjs.org/examples , we still have issue with 3.7, for now. by next week i hope getting sometime to fix it

fouss commented 11 months ago

hey, any news on this issue ? :)

JulianMar commented 10 months ago

@chakAs3 If you have some hint where to look. I could try to get it fixed!

bmulholland commented 10 months ago

@JulianMar See https://github.com/nuxt-modules/storybook/issues/428#issuecomment-1794448129

Code seems to be in the main Storybook repo, so I've posted an issue there too: https://github.com/storybookjs/storybook/issues/24746

chakAs3 commented 10 months ago

@JulianMar i will work on that now ! i will update you

pixleight commented 10 months ago

Checking back to see if this has any updates 😃

filiphazardous commented 10 months ago

@pixleight There has been an 0.2 version released - which solved a similar bug for me. It's worth a try. (Maintainer has had this bug reported a dozen times in different packages, so I guess he hasn't managed to give feedback on all the instances.)