Sorry, but you either have no stories or none are selected somehow.
If the problem persists, check the browser console, or the terminal you've run Storybook from.
The component failed to render properly, likely due to a configuration issue in Storybook. Here are some common causes and how you can address them:
Because Storybook works separately from your app, you'll need to configure it for your specific stack and setup. Below, explore guides for configuring Storybook with popular frameworks and tools. If you get stuck, learn how you can ask for help from our community.
Like with web applications, there are many ways to include CSS within Storybook. Learn more about setting up styling within Storybook.
Learn moreOften when a story doesn't render, it's because your component is expecting a specific environment or context (like a theme provider) to be available.
Learn moreTo link static files (like fonts) to your projects and stories, use the
staticDirs
configuration option to specify folders to load when
starting Storybook.
Now that you know the basics, let's explore other parts of Storybook that will improve your experience. This list is just to get you started. You can customise Storybook in many ways to fit your needs.
Auto-generate living, interactive reference documentation from your components and stories.
Learn morePublish your Storybook to review and collaborate with your entire team.
Learn moreEmbed your stories into Figma to cross-reference the design and live implementation in one place.
Learn more