[DS-5] Set up Storybook for the design system #3
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "feature/DS-5"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Ticket
DS-5 Set up Storybook for the design system
Summary
@storybook/react-vite+react-native-web— not@storybook/react-native,since there's no RN/Expo scaffold (no Metro, no simulator/device) in this repo's headless dev
container. This renders through the same web path any web consumer of this package already
takes.
src/tokens.ts) and derives theTailwind preset's
theme.extendfrom them, so the theme switcher has real values to switch.DS-7 itself is still open/undecided in Plane; these are adopted here as draft values to unblock
this ticket.
ThemeProviderdecorator,.storybook/) — explicitly dev-tooling only, not exported fromsrc/index.ts. Productiontheming for consumers stays compile-time-only via the Tailwind preset, per DS-3 option 1.
ExampleCardstory (stories/) since no real design-system components existyet — demonstrates the story-wiring pattern (
Meta/StoryObj, args) for future components tocopy. Its own
useTheme()+ inline-style approach is explicitly scaffolding only; realcomponents must style via NativeWind classNames from the Tailwind preset, not this context.
docker-compose.ymlstorybookservice — it's no longer profile-gated and nowruns permanently (
restart: unless-stopped), same asdev.and adding a new theme.
Found during manual Storybook verification: an exact-match ("react-native$") alias key left Vite's dependency optimizer pre-bundling the real react-native package (Flow syntax it can't parse) instead of resolving to react-native-web. A plain "react-native" key, plus handling both the array and object forms Storybook's own Vite config may already use for resolve.alias, fixes it.