Kickstarting libraries of shared React components for multiple teams
summary
Company turns six duplicated components into a mono-repo of reusable packages that six teams reuse daily, built with Storybook, Lerna, Flow, Rollup and published to npm or a private Verdaccio registry. Concrete practices include Atomic Design, explicit exported Flow types plus Danger checks to catch breaking changes, npm link for fast iteration, and using the module field for ES modules to enable tree-shaking. Performance indicators and adoption metrics prove the effort reduced repeated work and scaled across teams.
AI-written summary · about
chapters (9)
- 0:00Start
- 4:49Pre-requisites
- 5:44Package and distribute
- 10:03Advertise
- 13:01Encourage contribution
- 17:22Protect your users
- 20:55Split your packages
- 25:54Make your packages light
- 29:24rollup.js
related talks
33mKickstarting a library of internal React components for multiple teams
43mBuilding a component based library with React
24mCase Study: Creating a Component Library in React JS
07mBuilding Component Libraries for Cross Team Use with React
21mBuilding Cross-Platform Component Libraries for Web and Native with React
27mUp and Running with Universal Components
49mScalable Best Practices for Your Development Team
29mModularity and Monorepositories