Changing React Native... from within!
summary
Microsoft is fixing React Native’s developer experience by shipping concrete tools and core patches: rnx kit (30+ packages) adds a CLI and defaults, depth-check encodes tested version combinations to automate safe upgrades, and Metro plugins add symlink support, TypeScript validation, duplicate-package and cycle detection plus fast tree-shaking via esbuild. Work targets mono repos with ~5,000 external dependencies, reduces bundle size, surfaces platform-specific type errors, and aims to land more PRs through coordinated industry groups (Meta, Expo, Airbnb, Google, etc.).
AI-written summary · about
chapters (13)
- 0:00Intro
- 0:54Microsoft React Native
- 1:37Dev experience doesn't scale
- 4:58Changing the status quo
- 7:47Challenges
- 7:59Apps and experiences
- 9:44Staying up-to-date, at scale
- 16:48What does success look like?
- 20:43Focused on developer experience
- 22:22Meet the tools
- 28:30Command-line interface
- 30:14Straight to the source
- 31:15What did you learn today?
related talks
31mSolving a Tooling Problem For React Native
18mReact Native at Microsoft: A Journey of Strategic Adaptability and Innovation
24mTaking React Native to macOS
42mReact Native Panel & Q&A
34mMonorepo: React Web & React Native
37mPanel Discussion
59mOne Codebase to Rule Them All - Using React Native Everywhere
34mMonorepo: React Web & React Native