addon-info show Unknown component names
See original GitHub issueDescribe the bug When i run build-storybook after upgrade from 4.0.8 to 4.1.0-alpha.8 addon-info show me in Story Source section code like this:
<Unknown>
  <Unknown>
    <Text>
      Enter
    </Text>
  </Unknown>
</Unknown>
Expected behavior before upgrade code was like below
<Background>
  <Button>
    <Text>
      Enter
    </Text>
  </Button>
</Background>
and i use custom .storybook/.babelrc file with
   plugin:  "add-react-displayname"
System: “@storybook/addon-info”: “4.1.0-alpha.8”, “@storybook/addon-knobs”: “4.1.0-alpha.8”, “@storybook/addon-options”: “4.1.0-alpha.8”, “@storybook/cli”: “4.1.0-alpha.8”, “@storybook/react”: “4.1.0-alpha.8”, “react-scripts”: “2.1.1”,

Issue Analytics
- State:
 - Created 5 years ago
 - Comments:6 (1 by maintainers)
 
Top Results From Across the Web
addon-info show Unknown component names · Issue #4881
Describe the bug When i run build-storybook after upgrade from 4.0.8 to 4.1.0-alpha.8 addon-info show me in Story Source section code like ...
Read more >storybook-info - npm Package Health Analysis
When creating components, set the displayName static property to show the correct component name on static builds. storybook-info dependencies.
Read more >react storybook addon knobs not showing
I said the needed to create the file and on addon-notes that is a component as addon-knobb it says that. "Then create a...
Read more >Unknown Tracker : Bags, Bank, Inventory
Display Inventory Icon and/or Tooltip for unknown Motifs, Recipes, Furnishings, Stylepages and Runeboxes; Multiple accounts supported e.g. ...
Read more >:h vim-addon-manager-additional-documentation.txt
Shows addon information. Accepts both VAM script names and www.vim.org. script numbers. If neither succeeds the any-regex is used and compared.
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

Please check later versions of Storybook, it was already fixed.
I just noticed that the issue arises when u define your components something like:
export default () => {}but if you do something like:
it gets fixed