Building an Angular component Library
summary
Concrete outcome: a reusable Angular component library implemented as a monorepo with each component as its own project, published as npm packages. Uses ng-packagr to produce Angular Package Format artifacts, a private registry (Verdaccio) to host packages, and per-component semantic versioning so squads can upgrade independently. Includes unit tests, shared linting, a demo app and published demo documentation site; the library is in active use and reduces UI divergence across teams.
AI-written summary · about
chapters (8)
- 0:00Intro
- 1:40Context: KPN Grip
- 2:43Context: Multiple Teams
- 4:46Context: Tribe Model Pitfalls
- 6:37Solution: Component Library
- 8:44Ingredients
- 18:07Publishing flow
- 22:11Lessons Learned: Best Practices
related talks
26mLearnings from building a component library
24mCase Study: Creating a Component Library in React JS
41mManaging a (component) zoo - DIY web component catalogues
25mFrom Design Systems to Component Libraries
20mEngineering Scalable Angular Components
46mBuilding Reusable Components ... That Are Actually Reusable
44mBest Practices on building a UI component library for your company
01h 12mMake Web Development Fun Again, with Web Components
