How to publish a React Native component library
summary
Explains concrete portability pitfalls and fixes: assume overflow is hidden on Android, set text background to transparent, and prefer a custom ripple/touchable strategy (mentions react-native-platform-touchable and the ripple used in react-native-paper). Recommends shipping source + ESM/CJS/types (use package.json fields and the files list), automating builds with bob and releases with release-it, preferring TypeScript for libraries, baking in accessibility and RTL, and providing platform-specific fallbacks via Metro (.android/.ios/.native) files.
AI-written summary · about
chapters (14)
- 0:00Introduction
- 1:04UI library challenges
- 2:38Cross-platform differences
- 8:36Handling notch and safe areas
- 12:40Platform-specific code
- 14:18Responsive design
- 18:31Accessibility best practices
- 25:50RTL support
- 28:04Linking native libraries
- 28:59Documentation strategies
- 31:58Static type checking
- 34:02Code quality tools
- 35:31Publishing the library
- 39:56Maintenance advice
related talks
21mBuilding Cross-Platform Component Libraries for Web and Native with React
25mReact developers in a wild world of native apps
35mBridging the Gap: How to use React Native in existing large native code bases
26mUniversal Components & Deterministic Rendering
44mReact Native: how to succeed with your mobile app
59mOne Codebase to Rule Them All - Using React Native Everywhere
23mThe State of One Codebase For All The Platforms
39mFrom React to React Native