[Tracking] React-docgen related issues

[yannbf]

NOTE: For anybody who is unaware, a workaround for many (most?) of these issues is to set typescript.reactDocgen to react-docgen-typescript in .storybook/main.js. Learn more.

Describe the bug

This will serve as an umbrella issue where we document all the issues regarding react-docgen. It will be updated over time.

React-docgen related issues

Performance related

Preview Give feedback

1. [Bug]: Storybook 8 babel code generator takes forever to start up with material ui components and runs out of memory when trying to build #26543
   bug performance issue sev:S2 +3
   

Limitations

Preview Give feedback

1. [Bug]: 8.0.0 8.1.0-alpha2 Vite React ReferenceError in component resolution #26548
   bug needs triage +2
2. [Bug]: Prop Reference Error with Object Type Syntax in Storybook v8 #26406
   bug docgen upgrade:8.0 +3
3. [Bug]: Missing initializer in const declaration in preview.ts file related to Preview type #26467
   bug needs triage +2
4. [Bug]: Storybook 8 union type arguments values are shown as "union" instead of individual values. #26407
   +0
5. [Bug]: Storybook v8.0.0-alpha.16 unknown types #25909
   bug nextjs +2
   
6. [Bug]: react-docgen fails on match(regex) inside promise. #26652
   bug docgen needs more info react +4
7. https://github.com/storybookjs/storybook/discussions/26583
8. [Bug]: Controls can't display enum props #26745
   bug needs triage +2
9. [Bug]: build error using typescript decorators when upgrade react-vite to 8.0.6 #26780
   bug docgen react +3
10. [Bug]: v7 -> v8 controls tab is missing a lot of information #26496
    Stale bug docgen needs more info react +5

Reproduction

In order to assist the React docgen maintainer to fix as many of these issues as possible, here's a reproduction that shows all these scenarios, with options to run Storybook with both react-docgen and react-docgen-typescript for comparison:

https://stackblitz.com/edit/react-docgen-issues-and-limitations

[federico-ntr]

Just wanted to report an issue I opened some weeks ago regarding react-docgen.
I have opened an issue on react-docgen repo as well.

[PatrickMunsey]

I'm seeing a lot of these issue being ticked off and completed.

Adding the following tomain.js re enables autdocs to detect and generate controls with the correct name and description however the default value and type with correct input component is still broken.

Should I create a new issue and add to this list?

I haven't been able to find an existing issue for control input types in autodocs only being strings and objects instead of nice radio buttons or boolean toggles etc.

I mentioned this in another comment :
#28350 (reply in thread)