Kickstarting a library of internal React components for multiple teams

on YouTube ↗33m

" summary

A mono‑repo splits UI into atoms/molecules/organisms and ships reusable widgets plus data services and a modelizer, managed with Liana and published to a private registry vibrato; development happens in storybook, APIs carry flow types and commit‑based semantic versioning flags breaking changes to CI. Three prior attempts (Commando, Tapas, Component Studio) show what fails and why. Six host teams adopt the library and the project reports ~80% saved development cost, so the approach works.

AI-written summary · about

" chapters (7)

1. 0:00Introduction
2. 1:43Why we started this project
3. 3:08Examples
4. 8:18Tips
5. 13:30Breaking Changes
6. 17:30Return on Risk
7. 21:23Success

" related talks

• 32mKickstarting libraries of shared React components for multiple teamsSurya Ambrose · reactjsday 2019
• 43mBuilding a component based library with ReactFerry Kobus · Frontend United 2018
• 24mCase Study: Creating a Component Library in React JSKathryn Grayson Nanz · NationJS Frontrunners React 2019
• 07mReact components, atomic design and storybookEinar Afiouni · NDC Oslo 2017
• 46mBuilding Reusable Components ... That Are Actually ReusableCory House · Connect.Tech 2021
• 07mBuilding Component Libraries for Cross Team Use with ReactJoel Carras · JS Kongress 2016
• 29mUniversal ReactMike Grabowski · React Amsterdam 2017
• 26mLearnings from building a component libraryThomas Pink, Fabian Friedl · NG-DE Conference 2019