Cannot launch storybook UI, receiving multiple errors
See original GitHub issueDescribe the bug A clear and concise description of what the bug is.
To Reproduce I don’t know how to reproduce
Expected behavior To load the UI Screenshots this is my package.json
Code snippets
vendors~main.51373e64048002224644.bundle.js:30622 Uncaught TypeError: Cannot read property 'Consumer' of undefined
at ThemeProvider (vendors~main.51373e64048002224644.bundle.js:30622)
at renderWithHooks (vendors~main.51373e64048002224644.bundle.js:80002)
at mountIndeterminateComponent (vendors~main.51373e64048002224644.bundle.js:82084)
at beginWork (vendors~main.51373e64048002224644.bundle.js:82689)
at performUnitOfWork (vendors~main.51373e64048002224644.bundle.js:86376)
at workLoop (vendors~main.51373e64048002224644.bundle.js:86416)
at HTMLUnknownElement.callCallback (vendors~main.51373e64048002224644.bundle.js:67213)
at Object.invokeGuardedCallbackDev (vendors~main.51373e64048002224644.bundle.js:67263)
at invokeGuardedCallback (vendors~main.51373e64048002224644.bundle.js:67320)
at replayUnitOfWork (vendors~main.51373e64048002224644.bundle.js:85642)
vendors~main.51373e64048002224644.bundle.js:84181 The above error occurred in the <ThemeProvider> component:
in ThemeProvider (created by Manager)
in Manager (created by Context.Consumer)
in Location (created by QueryLocation)
in QueryLocation (created by Root)
in LocationProvider (created by Root)
in HelmetProvider (created by Root)
in Root
React will try to recreate this component tree from scratch using the error boundary you provided, LocationProvider.
logCapturedError @ vendors~main.51373e64048002224644.bundle.js:84181
vendors~main.51373e64048002224644.bundle.js:3086 Uncaught TypeError: Cannot read property 'Consumer' of undefined
at ThemeProvider (vendors~main.51373e64048002224644.bundle.js:30622)
at renderWithHooks (vendors~main.51373e64048002224644.bundle.js:80002)
at mountIndeterminateComponent (vendors~main.51373e64048002224644.bundle.js:82084)
at beginWork (vendors~main.51373e64048002224644.bundle.js:82689)
at performUnitOfWork (vendors~main.51373e64048002224644.bundle.js:86376)
at workLoop (vendors~main.51373e64048002224644.bundle.js:86416)
at renderRoot (vendors~main.51373e64048002224644.bundle.js:86499)
at performWorkOnRoot (vendors~main.51373e64048002224644.bundle.js:87406)
at performWork (vendors~main.51373e64048002224644.bundle.js:87318)
at performSyncWork (vendors~main.51373e64048002224644.bundle.js:87292)
vendors~main.51373e64048002224644.bundle.js:84181 The above error occurred in the <LocationProvider> component:
in LocationProvider (created by Root)
in HelmetProvider (created by Root)
in Root
Consider adding an error boundary to your tree to customize error handling behavior.
Visit https://fb.me/react-error-boundaries to learn more about error boundaries.
logCapturedError @ vendors~main.51373e64048002224644.bundle.js:84181
vendors~main.51373e64048002224644.bundle.js:87376 Uncaught TypeError: Cannot read property 'Consumer' of undefined
at ThemeProvider (vendors~main.51373e64048002224644.bundle.js:30622)
at renderWithHooks (vendors~main.51373e64048002224644.bundle.js:80002)
at mountIndeterminateComponent (vendors~main.51373e64048002224644.bundle.js:82084)
at beginWork (vendors~main.51373e64048002224644.bundle.js:82689)
at performUnitOfWork (vendors~main.51373e64048002224644.bundle.js:86376)
at workLoop (vendors~main.51373e64048002224644.bundle.js:86416)
at renderRoot (vendors~main.51373e64048002224644.bundle.js:86499)
at performWorkOnRoot (vendors~main.51373e64048002224644.bundle.js:87406)
at performWork (vendors~main.51373e64048002224644.bundle.js:87318)
at performSyncWork (vendors~main.51373e64048002224644.bundle.js:87292)
I have tried multiple times deleting my node_modules and yarn.lock I am working with a monorepository so I don’t know if that would make a difference
System:
- OS: Windows 10
- Browser: Chrome
- Framework: React
- Addons: a11y and notes
- Version: 5.0.11
Additional context Using yarn workspaces in a monerepo
Issue Analytics
- State:
- Created 4 years ago
- Comments:6 (2 by maintainers)
Top Results From Across the Web
Cannot launch storybook UI, receiving multiple errors #6760
Describe the bug. A clear and concise description of what the bug is. To Reproduce I don't know how to reproduce. Expected behavior...
Read more >How to troubleshoot storybook not loading stories?
Resave save the story file. It makes the component reappear in side panel, and then you can see the errors ...
Read more >Configure Storybook
Storybook is a frontend workshop for building UI components and pages in isolation ... See all the available fields below if you need...
Read more >Troubleshooting Common Errors - Gatsby
As you encounter errors while developing with Gatsby, it is likely you'll run into something that other users have already stumbled upon. Some...
Read more >Error Boundaries - React
A JavaScript error in a part of the UI shouldn't break the whole app. ... React 16 prints all errors that occurred during...
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 FreeTop 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
Top GitHub Comments
I’m experiencing a similar issue with Storybook 6.2.9
https://github.com/creativecommons/vocabulary/issues/895
i’m just going to close this. I ended up not using storybook in order to get my work done. If I end up using it in the future and run into these errors again I will opena new issue with more detailed information.