Component Driven Repo for a Component Driven World
summary
Argues that front ends must be split into independently versioned component scopes (examples: base-ui scope, e-commerce scope, separate repos for four stores) and shows a working demo shoe-store app composed from those packages. Uses bit (export/import, hosted or self‑hosted on bit.dev), mentions lerna, Nx and GitHub Codespaces as tooling tradeoffs, explains auto-tagging within a workspace, cites a 6‑month real‑world logo update pain and demonstrates that the approach reduces coupling and enables independent deploys.
AI-written summary · about
chapters (10)
- 0:00Start
- 7:33Frontend Monolith
- 10:51Packaging Components
- 19:25Support Team
- 20:28Design Team
- 29:58Your Component
- 30:51Organizations
- 32:54Encapsulated
- 34:38Reusable
- 41:18Component Driven
related talks
57mComponent Driven Repo for a Component Driven World
24mComponent Driven repo for a component driven world
20mTaking Component Driven One Step Further
44mIt’s all about components
21mShared Components Beyond the Design System
36mAngular, React, Vue and co: Harmoniously united by web components and micro apps?
29mModularity and Monorepositories
25mMicrofrontends: a Modern Approach to Complex Web Applications