| name | setup-react-native-storybook |
| description | Set up Storybook for React Native in Expo, React Native CLI, or Re.Pack projects. Use when adding Storybook to a project, configuring metro.config.js with withStorybook, creating .rnstorybook configuration files, setting up Storybook routes in Expo Router, configuring getStorybookUI, or adding the StorybookPlugin to a Re.Pack rspack/webpack config. Covers Expo, Expo Router, plain React Native CLI, and Re.Pack setups. |
React Native Storybook Setup
Add @storybook/react-native v10 to a React Native project.
Important: Detect the project's package manager (look for yarn.lock, pnpm-lock.yaml, or bun.lockb) and use it for all install/run commands instead of npm. The examples below use npm but substitute accordingly (e.g. yarn add instead of npm install, yarn storybook instead of npm run storybook). For Expo projects, use npx expo install (or bunx expo install, etc.) to install dependencies so Expo can resolve compatible versions.
For the init command, use <pm> create storybook with the flags shown below. Only npm needs -- before the flags. Never use npx/bunx etc for this.
Four setup flows based on project type:
- Expo (no router) - see references/expo-setup.md
- Expo with Expo Router - see references/expo-router-setup.md
- React Native CLI (no Expo) - see references/react-native-cli-setup.md
- Re.Pack (rspack/webpack) - see references/repack-setup.md
Flow Selection
- Project has
rspack.config or webpack.config and uses @callstack/repack -> Re.Pack
- Project has
app/ directory with _layout.tsx and uses expo-router -> Expo Router
- Project uses Expo but not file-based routing -> Expo
- Project uses
@react-native-community/cli with no Expo -> React Native CLI
Common Steps (all flows)
1. Run CLI Init
npm create storybook -- --type react_native --yes
This installs dependencies and creates .rnstorybook/ with main.ts, preview.tsx, and index.tsx.
2. Enable WebSockets in .rnstorybook/index.tsx
Update the generated .rnstorybook/index.tsx to enable WebSocket support. This is required for remote control and syncing with the Storybook web companion:
import AsyncStorage from '@react-native-async-storage/async-storage';
import { view } from './storybook.requires';
const StorybookUIRoot = view.getStorybookUI({
storage: {
getItem: AsyncStorage.getItem,
setItem: AsyncStorage.setItem,
},
enableWebsockets: true,
});
export default StorybookUIRoot;
If the project doesn't have @react-native-async-storage/async-storage, install it:
npm install @react-native-async-storage/async-storage
3. Update Story Globs in main.ts
The CLI generates a default stories glob in .rnstorybook/main.ts. Keep the existing glob and add an additional entry pointing to where UI components actually live in the project. Look for directories like components/, src/components/, src/, ui/, etc.:
const main: StorybookConfig = {
stories: [
'./stories/**/*.stories.?(ts|tsx|js|jsx)',
'../src/components/**/*.stories.?(ts|tsx|js|jsx)',
],
};
4. Configure Bundler
For Metro projects, wrap the metro config with withStorybook. For Re.Pack projects, add the StorybookPlugin to your rspack/webpack config. See the relevant reference file for details.
5. Create Entrypoint
How Storybook is rendered differs per flow - see the relevant reference file.
6. Run
npm run start
npm run ios
withStorybook Options (Metro)
module.exports = withStorybook(config, {
enabled: true,
configPath: './.rnstorybook',
useJs: false,
docTools: true,
liteMode: false,
websockets: { port: 7007, host: 'localhost' },
});
StorybookPlugin Options (Re.Pack)
new StorybookPlugin({
enabled: true,
configPath: './.rnstorybook',
useJs: false,
docTools: true,
liteMode: false,
websockets: 'auto',
});