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

Cannot launch storybook UI, receiving multiple errors #6760

Closed
forrestblade opened this issue May 10, 2019 · 6 comments
Closed

Cannot launch storybook UI, receiving multiple errors #6760

forrestblade opened this issue May 10, 2019 · 6 comments

Comments

@forrestblade
Copy link

Describe 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

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

@forrestblade
Copy link
Author

I'm at the point where I need to downgrade back to to 4.x.x so I can finish my work. The reason I was upgrading is I had a specific component that was crashing Storybook all together and I figured that upgrading might resolve that issue.

@shilman
Copy link
Member

shilman commented May 10, 2019

@forrestblade Are you trying to theme Storybook? If so, I'd suggest removing that part, since the stack trace is theming-related.

@shilman shilman added this to the 5.0.x milestone May 10, 2019
@forrestblade
Copy link
Author

No we aren't using any themes. I added the themes package in an attempt to resolve that issue

@shilman
Copy link
Member

shilman commented May 12, 2019

what version of react are you using?

@forrestblade
Copy link
Author

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.

@brylie
Copy link

brylie commented Jun 9, 2021

I'm experiencing a similar issue with Storybook 6.2.9

https://github.com/creativecommons/vocabulary/issues/895

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

No branches or pull requests

3 participants