Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Compatibility issues with Nuxt 3.7.x #75

Open
pixleight opened this issue Oct 13, 2023 · 7 comments
Open

Compatibility issues with Nuxt 3.7.x #75

pixleight opened this issue Oct 13, 2023 · 7 comments
Assignees

Comments

@pixleight
Copy link

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
Copy link
Contributor

chakAs3 commented Oct 20, 2023

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

@chakAs3 chakAs3 self-assigned this Oct 27, 2023
@fouss
Copy link

fouss commented Nov 3, 2023

hey, any news on this issue ? :)

@JulianMar
Copy link

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

@bmulholland
Copy link

@JulianMar See nuxt-modules/storybook#428 (comment)

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

@chakAs3
Copy link
Contributor

chakAs3 commented Nov 8, 2023

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

@pixleight
Copy link
Author

Checking back to see if this has any updates 😃

@filiphazardous
Copy link

@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.)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

6 participants