Uncaught Error: Singleton client API not yet initialized, cannot call addParameters
See original GitHub issueI have managed to get storybook running with start-storybook. I have also now managed to get the build compete. But when I open the generated SB page I get the following error:
iframe.778fe525.js:33 Uncaught Error: Singleton client API not yet initialized, cannot call addParameters
at addParameters (iframe.778fe525.js:33)
at iframe.778fe525.js:90
at Array.forEach (<anonymous>)
at iframe.778fe525.js:90
at Array.forEach (<anonymous>)
at iframe.778fe525.js:90
Has anyone seen something similar perhaps?
I am using vue3 on windows.
Issue Analytics
- State:
- Created 2 years ago
- Reactions:7
- Comments:22 (6 by maintainers)
Top Results From Across the Web
"Singleton client API not yet initialized" · Issue #10887 - GitHub
Uncaught Error : Singleton client API not yet initialized, cannot call addParameters after upgraded from 6.3.0-beta.16 to 17 #15210.
Read more >Error: Singleton client API not yet initialized... #13793 - Issuehunt
client_api.js:93 Uncaught Error: Singleton client API not yet initialized, cannot call addParameters at addParameters (client_api.js:93) at Object.
Read more >@storybook/client-api - npm
In order to appear to the store like the CSF API, a call to storiesOf().add() does the following: Tracks the story added in...
Read more >lib/client-api/src/ClientApi.ts - Storybook - Fossies
44 addParameters: `Instead, use \`export const parameters = {};\` in your ... 75 throw new Error(`Singleton client API not yet initialized, cannot call...
Read more >Storybook throwing errors - Stack Overflow
The error log is pointing out that your min-indent package may be missing from your node_modules folder for whatever reason. Error: Cannot ......
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
I finally found a solution to this here I will just copy the correct answer, as it solved this for once:
Thanks @develar
@IanVS that was a mixup when I was creating the repo. I’ve updated them all to
next
(on the repo above) and it’s the same issue.