Sharing a Codebase with React & React Native
summary
Attempting to share web and React Native code for Cleo ends with concrete tradeoffs: a simple symlinks fail with Metro bundler experiment works for web but breaks RN; turning the shared file into a package hits yarn workspaces hoisting pain — Metro config, CI/CD changes, dedupe and version mismatch headaches — and a few hours of work show the maintenance cost outweighs the tiny payoff, so code is duplicated and rewritten with strict TypeScript instead.
AI-written summary · about
chapters (10)
- 0:00Introduction
- 0:48History of Clio
- 2:06React Native
- 2:45Comparing Designs
- 3:20The Holy Grail
- 3:39The Challenge
- 4:00Simlinks
- 5:10Star Wars
- 5:28Engineering Principles
- 5:44Conclusion
related talks
34mMonorepo: React Web & React Native
34mMonorepo: React Web & React Native
59mOne Codebase to Rule Them All - Using React Native Everywhere
28mCross-Platform React
35mBridging the Gap: How to use React Native in existing large native code bases
35mReact Native & Rails, A Single Codebase for Web & Mobile
34mChanging React Native... from within!
36mThe sorcery of building a cross platform Design System architecture
