There are a few things to check with 'react-docgen-typescript' and Storybook + Vite, especially in a Turborepo setup:

• Storybook for React & Vite defaults to 'react-docgen', but you can switch to 'react-docgen-typescript' by setting reactDocgen: "react-docgen-typescript" in your config, which you’ve done. This is supported, but the integration can be fragile depending on builder and config details docs.
• The plugin that powers this (@joshwooding/vite-plugin-react-docgen-typescript) was recently updated for Vite 7 compatibility. Make sure you’re on Storybook 9.0.15+ and that this plugin is at least v0.6.1 in your lockfile PR.
• Advanced options like custom tsconfigPath and propFilter may not always propagate as expected under Vite. If you suspect these are being ignored, try simplifying your config (remove propFilter and custom tsconfigPath) to see if basic docgen works, then add options back one at a time docs.
• Double-check that your referenced tsconfig.json exists and is valid, and that your components use TypeScript types/interfaces in a way that docgen can parse.
• If you see no errors but still get no docs, try running Storybook with --debug-webpack (even with Vite, this can surface config issues) and look for any warnings about docgen or TypeScript.

There are also known architectural limitations: Storybook config files are always loaded as CommonJS, so ESM-only features (like import.meta) won’t work in config files issue.

If none of these steps help, let me know if you’re seeing any specific errors or warnings in your Storybook output—those details can help narrow down the root cause.

To reply, just mention @dosu.

^{How did I do? Good | Irrelevant | Incorrect | Verbose | Hallucination | Report 🐛 | Other}