Describe the bug

When attempting to document a new component, component search fails

BUG:
A large RED popup window with white text beginning
An error occurred while searching for components in the project. ENAMETOOLONG: name too long, scandir '/

IMPACT:
No components can be documented using the UI
may occur for any user on any host

SYMPTOMTS:
—1 the paths listed are away from the project directory but in the root file-system directory in which the project is located
—2 Storyboard is for some reason scanning directories outside the project directory
—3 The BUG can occur for any user on any host

Apparently, scanning is not filtered for cyclic symbolic paths. A map of absolute paths is going to be required
file systems do not guarantee the path to a particular node being unique even when symlinks are resolved, so a limit on recursion must be implemented, like Go limits to 100 symlinks

CAUSE:
some permitted use of symlinks in the file system that Storybook decides to scan but is unable to successfully complete

Reproduction link

N/A

Reproduction steps

install vanilla storybook
on browser Storybook page, click +next to Find Components search box
In lightbox Add a new story ./components/**/*.tsx search box, type a character

System

macOS 14.5 vite React Storybook 8.1+

Additional context

No response