addon-docs Error: Cannot read property 'content' of undefined
See original GitHub issueHello everyone. I’m using the newest storybook/react with addon-docs, both version 5.2.0-beta.10. Right now I have a problem running the example from the official Storybook Docs: Technical Preview google docs. When I click Docs panel I get an error Cannot read property 'content' of undefined
Bug
Steps to reproduce
Configure the new Storybook beta with Docs addon and TypeScript. Run Storybook and click Docs panel.
Please specify which version of Storybook and optionally any affected addons that you’re running
- @storybook/react 5.2.0-beta.10
- @storybook/addon-docs 5.2.0-beta.10
Screenshots / Screencast / Code Snippets (Optional)
Storybook config.js
Storybook presets.js
Story
Example Component is a simple div
with Hello
text in it.
Issue Analytics
- State:
- Created 4 years ago
- Reactions:11
- Comments:30 (7 by maintainers)
Top Results From Across the Web
Storybook: Addon-Docs Cannot read property 'classes' of ...
Having added, and configured, @storybook/addon-docs the Storybook Docs page displays: “Cannot read property 'classes' of undefined” in the ...
Read more >storybook typeerror: cannot read properties of undefined ...
The TypeError: Cannot read properties of undefined (reading 'type') exception occurs in storybook when one defines the argTypes in the default export object ......
Read more >storybook/addon-docs - npm
sourceLoaderOptions is an object for configuring @storybook/source-loader . When set to null it tells docs not to run the source-loader at all, ...
Read more >Storybook error: Cannot read property 'createElement' of ...
However, it displays the following error: Cannot read property 'createElement' of undefined. Here is my main.js config:
Read more >[6.2.0-beta.1] Angular library not rendering without ... - Issuehunt
... error message: zone.js:690 Unhandled Promise rejection: Cannot read property 'id' of undefined ; Zone: <root> ; Task: Promise.then ; Value: TypeError: ...
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
Just got it on
5.3.17
. Removing node_modules and yarn.lock helped. (cc @viniciusdacal)Had this issue and it was indeed a duplication issue with emotion. Upgrading our (pinned) emotion dependencies fixed the problem for us. I know that the emotion team is working on providing runtime warnings for these issues like react does.
NB! I didn’t delete the
yarn-lock
so only got a minor change in that file.