React Native Storybook Upgrades
Upgrade one supported version step at a time. Do not jump from an older major directly to the latest release in a single pass.
Rules
- Detect the project's package manager first and use it consistently.
- Detect the currently installed Storybook version from
package.json, lockfiles, and config files before editing anything.
- Apply exactly one migration step per run. If a project is multiple versions behind, complete the next hop, verify it, and then report the next required hop.
- During the
6.5.x -> 7.6.x step, convert any remaining storiesOf stories to CSF instead of preserving compatibility mode.
- Preserve the project's existing app structure. Only make the migration changes required for the current step.
Version Detection
Look at these signals together:
package.json versions for @storybook/react-native, storybook, @storybook/react, and @storybook/addon-ondevice-*- Whether the config folder is
.storybook/ or .rnstorybook/
- Metro config imports such as
metro/withStorybook, metro/withStorybookConfig, or default-vs-named withStorybook
- Story format usage: CSF vs
storiesOf
- Generated file names such as
storybook.requires.js vs storybook.requires.ts
If the version is ambiguous, stop and clarify the current installed version instead of guessing.
Migration Selection
Use exactly one reference file:
9.x -> 10.x: references/from-9-to-10.md8.x -> 9.x: references/from-8-to-9.md7.6.x -> 8.3.x: references/from-7-6-to-8-3.md6.5.x -> 7.6.x: references/from-6-5-to-7-6.md5.3.x -> 6.5.x: references/from-5-3-to-6-5.md
Workflow
- Confirm the current Storybook version and whether the repo uses Expo, Expo Router, React Native CLI, or Re.Pack.
- Pick the next migration step only. Never bundle multiple major upgrades together.
- Apply the dependency, config, and source-file changes from the matching reference.
- Regenerate
storybook.requires or restart Metro when that step requires it.
- Run the smallest useful verification available for the repo, such as the generation script, tests, lint, or the local Storybook app launch path.
- If the repo still is not on the user's target version, stop with a clear note describing the next required migration step.
Output Expectations
When you finish a migration step, report:
- The version hop that was completed
- The files and config surfaces that changed
- The verification you ran, or what you could not run
- The next required migration hop, if the project is still behind
1---2name: upgrading-react-native-storybook3description: Incrementally upgrade React Native Storybook across the supported migration paths. Use when upgrading `@storybook/react-native` projects from 5.3.x to 6.5.x, 6.5.x to 7.6.x, 7.6.x to 8.3.x, 8.x to 9.x, or 9.x to 10.x. Detect the currently installed Storybook version, choose only the next migration step, update dependencies and config, regenerate `storybook.requires`, convert remaining `storiesOf` stories to CSF during the `6.5.x -> 7.6.x` upgrade, and stop after a single version hop instead of jumping multiple major versions at once.4---5
6# React Native Storybook Upgrades
7
8Upgrade one supported version step at a time. Do not jump from an older major directly to the latest release in a single pass.
9
10## Rules
11
12- Detect the project's package manager first and use it consistently.
13- Detect the currently installed Storybook version from `package.json`, lockfiles, and config files before editing anything.
14- Apply exactly one migration step per run. If a project is multiple versions behind, complete the next hop, verify it, and then report the next required hop.
15- During the `6.5.x -> 7.6.x` step, convert any remaining `storiesOf` stories to CSF instead of preserving compatibility mode.
16- Preserve the project's existing app structure. Only make the migration changes required for the current step.
17
18## Version Detection
19
20Look at these signals together:
21
22- `package.json` versions for `@storybook/react-native`, `storybook`, `@storybook/react`, and `@storybook/addon-ondevice-*`
23- Whether the config folder is `.storybook/` or `.rnstorybook/`
24- Metro config imports such as `metro/withStorybook`, `metro/withStorybookConfig`, or default-vs-named `withStorybook`
25- Story format usage: CSF vs `storiesOf`
26- Generated file names such as `storybook.requires.js` vs `storybook.requires.ts`
27
28If the version is ambiguous, stop and clarify the current installed version instead of guessing.
29
30## Migration Selection
31
32Use exactly one reference file:
33
341. `9.x -> 10.x`: [references/from-9-to-10.md](references/from-9-to-10.md)
352. `8.x -> 9.x`: [references/from-8-to-9.md](references/from-8-to-9.md)
363. `7.6.x -> 8.3.x`: [references/from-7-6-to-8-3.md](references/from-7-6-to-8-3.md)
374. `6.5.x -> 7.6.x`: [references/from-6-5-to-7-6.md](references/from-6-5-to-7-6.md)
385. `5.3.x -> 6.5.x`: [references/from-5-3-to-6-5.md](references/from-5-3-to-6-5.md)
39
40## Workflow
41
421. Confirm the current Storybook version and whether the repo uses Expo, Expo Router, React Native CLI, or Re.Pack.
432. Pick the next migration step only. Never bundle multiple major upgrades together.
443. Apply the dependency, config, and source-file changes from the matching reference.
454. Regenerate `storybook.requires` or restart Metro when that step requires it.
465. Run the smallest useful verification available for the repo, such as the generation script, tests, lint, or the local Storybook app launch path.
476. If the repo still is not on the user's target version, stop with a clear note describing the next required migration step.
48
49## Output Expectations
50
51When you finish a migration step, report:
52
53- The version hop that was completed
54- The files and config surfaces that changed
55- The verification you ran, or what you could not run
56- The next required migration hop, if the project is still behind
storybookjs