How to Evolve a Component Library Without Breaking It
summary
A Mail.ru team describes managing a shared UI component library used across projects and the repeated breakages when developers customized it. They explain their solution approach and tools used to prevent regressions, specifically naming Storybook, BackstopJS, Jest, Webdriver.io, and TypeScript.
AI-written summary · about
chapters (8)
- 0:00Introduction
- 7:25Component library problems
- 11:05CSS screenshot testing
- 13:37Storybook development
- 21:20JavaScript testing coverage
- 25:16Test-driven development
- 30:15Summary and future plans
- 44:27Q&A
related talks
25mFrom Design Systems to Component Libraries
26mLearnings from building a component library
44mBest Practices on building a UI component library for your company
24mCase Study: Creating a Component Library in React JS
46mBuilding Reusable Components ... That Are Actually Reusable
33mKickstarting a library of internal React components for multiple teams
14mBuilding a component library with React, Vue, Angular or WebComponents
28mDesign Decisions for the Components Library
