-
-
Notifications
You must be signed in to change notification settings - Fork 97
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
storybook@^6.2.0 release breaks @nuxtjs/storybook #252
Comments
I confirm @lihbr workaround works. |
Have the same since yesterday ;(( |
This will fix in v3.4. |
Thanks for the heads up @farnabaz, can we consider that one?
|
I guess this has been fixed with version 4? @farnabaz do you want to publish a patch for version 3 users that aren't yet on Nuxt 2.15.3+ or is it "good enough" to tell them to rely on the aforementioned workaround? Let me know, happy to help on a PR!
|
It's good idea to release a patch for v3 users @lihbr |
Cheers~ #260 |
Hey! Basically Storybook released a minor that breaks the module. I'm sorry for not submitting a really comprehensive issue, I'm a bit in a hurry right now, hit me up if anything!
Version
@nuxtjs/storybook:
v3.3.1
nuxt:
v2.15.3
node:
v14.15.3
npm:
v6.14.9
yarn:
v1.22.10
Reproduction Link
N/A
Steps to reproduce
npx create-nuxt-app repro-252
cd repro-252
yarn add --dev @nuxtjs/storybook
(or:npm install --save-dev @nuxtjs/storybook
npx nuxt storybook
What is Expected?
@nuxtjs/storybook
should be working.What is actually happening?
Workaround
For anyone experiencing the same issue, in the meantime you should be able to fix it this way:
@storybook/vue@6.1.21
(and pin other addons to the same version) in yourpackage.json
vue-loader@15.9.6
to dev dependencies.Anything else
I tested on Windows and MacOS and ended up with the same output.
Since Storybook doesn't seem to commit to SemVer fully perhaps we should use the tilde range instead of the caret one for referencing its dependencies? This will prevent the module to break on its own every now and then?
cc @arnaudlewis
The text was updated successfully, but these errors were encountered: