Session Information
Which Vue Validation Library Should We Really Use? The Limits of Self-Made Validation and How I Finally Moved On
Our product, built on Vue 3, had relied for years on a custom-built validation logic. However, over time, this homegrown solution began to show its limitations. A lack of documentation, inconsistent specifications, and the complexity of our proprietary setup all contributed to a growing maintenance burden. Eventually, the system became a significant source of technical debt that could no longer be ignored.
In this session, we'll walk you through how we confronted this issue. We'll share how we evaluated major Vue validation libraries—like Vuelidate, vee-validate, and Zod—what criteria guided our decision, and how we ultimately chose and implemented a new solution.
Beyond just selecting a library, we'll discuss the tangible benefits we gained from the transition: comprehensive official documentation, ease of learning, and improved maintainability.
We'll also dive into real-world challenges we faced during the migration from our legacy validation system, strategies for partial coexistence, and phased rollout methods—highlighting how we bridged the gap between ideal plans and practical constraints.
This talk is especially relevant for:
Developers struggling with the limitations of custom validation logic
Teams considering introducing a validation library in a Vue 3 environment
Our goal is to share insights that can help you tackle technical debt and move toward a healthier, more sustainable development experience.
neginasu
Which Vue Validation Library Should We Really Use? The Limits of Self-Made Validation and How I Finally Moved On
Our product, built on Vue 3, had relied for years on a custom-built validation logic. However, over time, this homegrown solution began to show its limitations. A lack of documentation, inconsistent specifications, and the complexity of our proprietary setup all contributed to a growing maintenance burden. Eventually, the system became a significant source of technical debt that could no longer be ignored.
In this session, we'll walk you through how we confronted this issue. We'll share how we evaluated major Vue validation libraries—like Vuelidate, vee-validate, and Zod—what criteria guided our decision, and how we ultimately chose and implemented a new solution.
Beyond just selecting a library, we'll discuss the tangible benefits we gained from the transition: comprehensive official documentation, ease of learning, and improved maintainability.
We'll also dive into real-world challenges we faced during the migration from our legacy validation system, strategies for partial coexistence, and phased rollout methods—highlighting how we bridged the gap between ideal plans and practical constraints.
This talk is especially relevant for:
Developers struggling with the limitations of custom validation logic
Teams considering introducing a validation library in a Vue 3 environment
Our goal is to share insights that can help you tackle technical debt and move toward a healthier, more sustainable development experience.