Rewriting for that 1000th Use Case – A Vue Component Story
summary
Vue-Multiselect has over 3,700 stars and 1 million downloads in 12 months but carries ~70 open issues; most problems come from early design choices (local cloning, scoped CSS, mixins) rather than syntax bugs. Tests are heavy—about 1,700 lines and ~100 cases with ~93% coverage—yet releases feel unsafe. The new v3 approach splits a renderless core (state + methods) from composed UI pieces (options, wrapper, values, input) using scoped slots so you can use the default UI or replace parts; repo on the v3 branch, pre-alpha.
AI-written summary · about
chapters (17)
- 0:00Introduction
- 0:57Vue Multi-Select library
- 2:25Lessons learned from issues
- 4:58Testing and maintenance challenges
- 6:04CSS scoping and styling pitfalls
- 7:10Mixins vs component extraction
- 8:13Focus state and accessibility
- 9:17Composition vs configuration
- 12:28Avoiding feature creep
- 14:44Exploring React Select and Downshift
- 16:54Finding the right balance
- 18:00New architecture with renderless components
- 20:13Default composition and backward compatibility
- 21:40Slot composition and customization
- 22:21Benefits of modular components
- 23:27Current status and next steps
- 23:49Q&A
