Set up Storybook for React Projects
This guide will walk you through setting up Storybook for React projects in your Nx workspace.
Set up Storybook in your workspaceYou 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.
Generate Storybook Configuration for a React project
You can generate Storybook configuration for an individual React project with this command:
nx g @nrwl/react:storybook-configuration project-name
Nx React Storybook Preset
@nrwl/react
ships with a Storybook preset to make sure it uses the very same configuration as your Nx React application. When you generate a Storybook configuration for a project, it'll automatically add the preset to your configuration.
const rootMain = require('../../../.storybook/main');
module.exports = {
...rootMain,
addons: [...rootMain.addons, '@nrwl/react/plugins/storybook'],
...
};
Auto-generate Stories
The @nrwl/react:storybook-configuration
generator has the option to automatically generate *.stories.ts
files for each component declared in the library.
<some-folder>/
├── my.component.ts
└── my.component.stories.ts
You can re-run it at a later point using the following command:
nx g @nrwl/react:stories <project-name>
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 @nrwl/react:stories feature-ui
and the result would be the following:
<workspace name>/
├── .storybook/
├── apps/
├── libs/
│ ├── feature/
│ │ ├── ui/
| | | ├── .storybook/
| | | ├── src/
| | | | ├──lib
| | | | | ├──my-button
| | | | | | ├── my-button.component.ts
| | | | | | ├── my-button.component.stories.ts
| | | | | | └── etc...
| | | | | └── etc...
| | | ├── README.md
| | | ├── tsconfig.json
| | | └── etc...
| | └── etc...
| └── etc...
├── nx.json
├── package.json
├── README.md
└── etc...
Cypress tests for Stories
The storybook-configuration
generator gives the option to set up an e2e Cypress app that is configured to run against the project's Storybook instance.
To launch Storybook and run the Cypress tests against the iframe inside of Storybook:
nx run project-name-e2e:e2e
The url that Cypress points to should look like this:
'/iframe.html?id=buttoncomponent--primary&args=text:Click+me!;padding;style:default'
buttoncomponent
is a lowercase version of theTitle
in the*.stories.ts
file.primary
is the name of an individual story.style=default
sets thestyle
arg to a value ofdefault
.
Changing args in the url query parameters allows your Cypress tests to test different configurations of your component. You can read the documentation for more information.
Example Files
*.stories.tsx file
import { Story, Meta } from '@storybook/react';
import { Button, ButtonProps } from './button';
export default {
component: Button,
title: 'Button',
} as Meta;
const Template: Story<ButtonProps> = (args) => <Button {...args} />;
export const Primary = Template.bind({});
Primary.args = {
text: 'Click me!',
padding: 0,
style: 'default',
};
Cypress test file
Depending on your Cypress version, the file will end with .spec.ts or .cy.ts
describe('shared-ui', () => {
beforeEach(() =>
cy.visit(
'/iframe.html?id=buttoncomponent--primary&args=text:Click+me!;padding;style:default'
)
);
it('should render the component', () => {
cy.get('storybook-trial-button').should('exist');
});
});
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