Component Driven Repo for a Component Driven World
summary
Argues that front-end monoliths break at scale and shows a working demo that builds four storefronts (shoe, perfume, electronics, sports) from independently versioned components using Bit, with scopes as domain packages, per-component CI and ownership, and the ability to import component source into a workspace to fix and re-export. Highlights real pain: one company spends six months updating a logo across apps. Covers tooling tradeoffs (lerna, nx, module federation) and config-as-component, aiming for component driven repos and loosely coupled reusable UI.
AI-written summary · about
chapters (25)
- 0:00Introduction and speaker bio
- 1:01Personal story and context
- 2:38The state of modern web development
- 4:05The evolution of architecture
- 5:28Front-end monolithic challenges
- 7:57Solutions: packaging and limitations
- 12:10The monorepo debate
- 16:45Feedback and common pain points
- 18:56Redefining team ownership
- 21:13Scopes and project structure
- 23:52Achieving team autonomy
- 25:40Building an independent ecosystem
- 27:48Practical component composition
- 30:42Versioning and component reuse
- 32:20The component-as-a-product mindset
- 34:07Benefits of the driven approach
- 35:47Technical characteristics of components
- 38:17Documentation and trust
- 40:23Real-world scaling and history
- 42:23Monorepos vs. decoupled code
- 44:07Standardization through components
- 45:47Demo and final considerations
- 47:41Core principles of independent components
- 50:39Closing thoughts and resources
- 51:39Q&A session
related talks
24mComponent Driven repo for a component driven world
55mComponent Driven Repo for a Component Driven World
20mTaking Component Driven One Step Further
44mIt’s all about components
21mShared Components Beyond the Design System
29mModularity and Monorepositories
36mAngular, React, Vue and co: Harmoniously united by web components and micro apps?
33mKickstarting a library of internal React components for multiple teams