-
-
Notifications
You must be signed in to change notification settings - Fork 9.9k
Description
Describe the bug
When a user attempts to install Storybook and selects the React Native Web option, the examples provided are inconsistent across the different components. For instance, the Header and Button component stories use the Meta and Story format with the satisfies type annotations, while the Page component story uses the export default and doesn't use the satisfies type annotations. This inconsistency can lead to confusion for users who are new to Storybook or unfamiliar with the different story formats and which format is recommended for React Native Web projects. Additionally, there are still leftover FIXME comments in the template files (e.g., Page.stories.tsx) that should be removed to avoid confusion for users who may not understand the context of those comments or whether they need to take any action based on them.
Reproduction link
N/A
Reproduction steps
- Create a new Expo project with
npx create-expo-app@latest - Run
npx storybook@latest initand select the React Native Web option - Select any of the available options (i.e., Development, or Recommended)
- Observe the inconsistencies in the generated story templates for the different components in the
.storybook/storiesdirectory, as well as the leftover comments in some of the template files.
System
|
|
| Storybook Environment Info:
|
| System:
| OS: Windows 11 10.0.26200
| CPU: (16) x64 AMD Ryzen 7 7435HS
| Binaries:
| Node: 24.10.0 - C:\nvm4w\nodejs\node.EXE
| Yarn: 4.12.0 - C:\Program Files (x86)\Yarn\bin\yarn.CMD <----- active
| npm: 11.6.1 - C:\nvm4w\nodejs\npm.CMD
| pnpm: 7.13.6 - C:\nvm4w\nodejs\pnpm.CMD
| Browsers:
| Chrome: 144.0.7559.133
| Edge: Chromium (140.0.3485.54)
| npmPackages:
| @storybook/addon-a11y: ^10.2.7 => 10.2.7
| @storybook/addon-docs: ^10.2.7 => 10.2.7
| @storybook/addon-vitest: ^10.2.7 => 10.2.7
| @storybook/react-native-web-vite: ^10.2.7 => 10.2.7
| eslint-plugin-storybook: ^10.2.7 => 10.2.7
| storybook: ^10.2.7 => 10.2.7Additional context
No response