Revamping VueMultiselect Using Vue 3 and TypeScript

[akki-jat]

🛠 Rewriting VueMultiselect for Vue 3 with TypeScript Integration

As Vue 3 continues to become the default across the ecosystem, many Vue 2 components need a serious overhaul—not just for compatibility, but to take advantage of the Composition API, improved TypeScript support, and performance gains. One such component is VueMultiselect, which is widely used but was originally crafted for Vue 2.

🔄 Why Rewrite?

• Vue 3 migration: Vue 2 syntax is becoming legacy. Migrating allows access to modern features like the Composition API.
• TypeScript adoption: Strong typing helps catch bugs early, improves IDE support, and makes large-scale maintenance easier.
• Performance upgrades: Vue 3 introduces faster rendering and better memory handling, which benefit complex UI components like multiselects.

🧩 Goals of the Rewrite

• Maintain existing functionality: Retain features users rely on (filtering, tagging, asynchronous options).
• Improve code modularity: Split concerns using the Composition API for better maintainability.
• Enhance customization: Make slots, props, and events more intuitive and well-documented.
• Add TypeScript typings: Create type-safe interfaces for props and events for better developer experience.

⚙️ Key Challenges

• Rewriting without regressions: Keeping behavior consistent during architectural shifts.
• Balancing flexibility vs. simplicity: VueMultiselect supports many use cases—rewriting can easily get bloated.
• Community adoption: Encouraging migration to the rewritten version without disrupting current projects.

[pczarn]

How may I help accomplish this?