-
-
Notifications
You must be signed in to change notification settings - Fork 9.4k
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
Uncaught Error: Singleton client API not yet initialized, cannot call addParameters after upgraded from 6.3.0-beta.16 to 17 #15210
Comments
fixed with 6.3.0-rc.4 and vite builder 0.0.8 |
@litan1106 I've just upgraded from We have a custom webpack config so I assume that's got something to do with it? |
My team is running into the same issue after upgrading today. |
I am seeing the same issue as well after building with vite-builder and vue3 project. |
Please file Vite-related issues in https://github.com/eirslett/storybook-builder-vite/ Thank you! 🙏 |
Ours isn't vite related @shilman - can you set my expectations here on what will happen next please? |
I can post some of our config if that would help? Don't have a repo to share with you. Or open a new issue? |
Here's the error we are getting
|
@sadir Can you please create a reproduction by running |
Same here when upgrading to 6.3. Removing all addons makes it work — except the postcss addon, that doesn't trigger this error. The addons I've tried adding that trigger this are links, essentials and docs. |
Upgrading to 6.3.2 seems to have fixed this issue for us, whatever it was! |
I'm getting the same error after upgrading from 6.1.11. to 6.3.2. I've also tried upgrading to 6.4.0-alpha.12 (with webpack 5) and the result is same, except now I'm also getting this in console: |
Hey I also ran into this issue after upgrading all packages to 6.3.2. This seems to be the same problem as #10887, so I ran
And the error is gone (for now). Here are the Storybook packages I'm using
And it seems even on a fresh |
Thanks @jaakerisalu but it didn't help my case. I've seen issue #10887 but that didn't help me either. |
I encountered this issue (again after several times in the past) after updating to v6.4.1. Removing any webpack modifications fixed the issue. Not sure what caused it to begin with. However, this also made me realize that most of our webpack modifications were unnecessary, since nowadays storybook has many things covered via presets |
Im seeing this issue with Cleaned node_modules and lock file |
The text was updated successfully, but these errors were encountered: