# before plugin api docs where stuck in `api` section which doesn't make sense # after move plugin api docs into `guides` section and add redirect for better discoverability
5.0 KiB
| title | description |
|---|---|
| Set up Storybook for React Projects | This guide explains how to set up Storybook for React projects in your Nx workspace. |
Set up Storybook for React Projects
This guide will walk you through setting up Storybook for React projects in your Nx workspace.
{% callout type="warning" title="Set up Storybook in your workspace" %} You first need to set up Storybook for your Nx workspace, if you haven't already. You can read the Storybook plugin overview guide to get started. {% /callout %}
Generate Storybook Configuration for a React project
You can generate Storybook configuration for an individual React project by using the @nx/react:storybook-configuration generator, like this:
nx g @nx/react:storybook-configuration project-name
Auto-generate Stories
The @nx/react:storybook-configuration generator has the option to automatically generate *.stories.ts|tsx files for each component declared in the library. The stories will be generated using Component Story Format 3 (CSF3).
<some-folder>/
├── my-component.tsx
└── my-component.stories.tsx
If you add more components to your project, and want to generate stories for all your (new) components at any point, you can use the @nx/react:stories generator:
nx g @nx/react:stories --project=<project-name>
{% callout type="note" title="Example" %}
Let's take for a example a library in your workspace, under libs/feature/ui, called feature-ui. This library contains a component, called my-button.
The command to generate stories for that library would be:
nx g @nx/react:stories --project=feature-ui
and the result would be the following:
<workspace name>/
├── apps/
├── libs/
│ ├── feature/
│ │ ├── ui/
| | | ├── .storybook/
| | | ├── src/
| | | | ├──lib
| | | | | ├──my-button
| | | | | | ├── my-button.tsx
| | | | | | ├── my-button.stories.tsx
| | | | | | └── etc...
| | | | | └── etc...
| | | ├── README.md
| | | ├── tsconfig.json
| | | └── etc...
| | └── etc...
| └── etc...
├── nx.json
├── package.json
├── README.md
└── etc...
{% /callout %}
Example Files
Let's take for a example a library in your workspace, under libs/feature/ui, called feature-ui with a component, called my-button.
Let's say that your component code looks like this:
export interface MyButtonProps {
text: string;
padding: number;
disabled: boolean;
}
export function MyButton(props: MyButtonProps) {
return (
<button disabled={props.disabled} style={{ padding: props.padding }}>
{props.text}
</button>
);
}
export default MyButton;
Story file
The @nx/react:storybook-configuration generator would generate a Story file that looks like this:
import type { Meta, StoryObj } from '@storybook/react';
import { MyButton } from './my-button';
import { within } from '@storybook/testing-library';
import { expect } from '@storybook/jest';
const meta: Meta<typeof MyButton> = {
component: MyButton,
title: 'MyButton',
};
export default meta;
type Story = StoryObj<typeof MyButton>;
export const Primary = {
args: {
text: '',
padding: 0,
disabled: false,
},
};
export const Heading: Story = {
args: {
text: '',
padding: 0,
disabled: false,
},
play: async ({ canvasElement }) => {
const canvas = within(canvasElement);
expect(canvas.getByText(/Welcome to MyButton!/gi)).toBeTruthy();
},
};
Notice the interaction test on the second story, inside the play function. This just tests if the default text that appears on generated components exists in the rendered component. You can edit this test to suit your needs. You can read more about interaction tests here.
More Documentation
You can find all Storybook-related Nx topics here.
For more on using Storybook, see the official Storybook documentation.
Migration Scenarios
Here's more information on common migration scenarios for Storybook with Nx. For Storybook specific migrations that are not automatically handled by Nx please refer to the official Storybook page