Monorepo: React Web & React Native
summary
Claim: sharing business logic between React web and React Native speeds development but adds real costs: npm link fails for RN, Metro bundler refuses parent folders, and native dependency versions collide. Built a Lerna + workspace setup that takes about a week to stabilize and sometimes yields 80% -> 30% code sharing as UI complexity grows. Also calls out styling, third‑party native components, platform‑specific storage and build quirks as the concrete blockers to shipping cross‑platform code.
AI-written summary · about
chapters (16)
- 0:00React Alicante
- 0:573x engineer
- 3:11Where are you
- 4:23Classic Case
- 4:36Technologies
- 5:33People Funnel
- 9:09React Promise
- 11:08Monorepo
- 14:58Example
- 17:43lerna.json
- 19:01Manage dependencies
- 24:12WHEN PEOPLE ASK ME
- 26:30Potential issues
- 30:58What to expect
- 31:42The End
- 33:38Thank you
related talks
34mMonorepo: React Web & React Native
28mCross-Platform React
07mSharing a Codebase with React & React Native
35mBridging the Gap: How to use React Native in existing large native code bases
46mReact Native for Web Panel Discussion
35mReact Native & Rails, A Single Codebase for Web & Mobile
25mGoing Native
21mBuilding Cross-Platform Component Libraries for Web and Native with React
