vee-validate VS zod

In this blog post I am exploring the client-side form validation with Vee-validate (https://vee-validate.logaretm.com/v4/) and vee-validate/rules (https://www.npmjs.com/package/@vee-validate/rules).

The Vue ecosystem is packed with many great form validation libraries, VeeValidate, Vuelidate, and FormKit just to name a few.

The two I heard of are Vuelidate and Vee-validate. Any opinion? Thanks.

Sorry if this comes off harsh. I think having a collection of built-in validators are nice, but there's also very solid libraries like Zod or Yup that have that feature nailed down. In the end, I don't feel like this library does all that much to justify it's existance in the vanilla case and especially in the Vue case. Here's some specific criticisms that I think would improve the library, though even if these items were fixed I would feel like it's pretty far off from being as helpful than existing libraries, e.g. vee-validate for Vue which allows for dynamic field generation while also supporting validation through Yup allowing for more complex cross-field validation.

VeeValidate

Ever used vee-validate? It is a nice form validation library and now with the help of composition API got even stronger.

You could try looking into VeeValidate, as it's probably the most similar in terms of hook usage.

I use VeeValidate for form validation. Is there any plugin or built-in feature in Quasar for replacing this package?

Zod is an open-source schema declaration and validation library that emphasizes TypeScript. It can refer to any data type, from simple to complex. Zod eliminates duplicative type declarations by inferring static TypeScript types and allows easy composition of complex data structures from simpler ones. It has no dependencies, is compatible with Node.js and modern browsers, and has a concise, chainable interface. Zod is lightweight (8kb when zipped), immutable, with methods returning new instances. It encourages parsing over validation and is not limited to TypeScript but works well with JavaScript as well.

Zod is a TypeScript-first schema declaration and validation library. It helps create schemas for any data type and is very developer-friendly. Zod has the functional approach of "parse, don't validate." It supports coercion in all primitive types.

Link: https://zod.dev/

You can check out their documentation here.

You can learn more about Zod on their website here.

In JS, it's a good idea anyway to use some JSON parsing library instead of JSON.parse.

With Zod, you can use z.bigint() parser. If you take the "parse any JSON" snippet https://zod.dev/?id=json-type and change z.number() to z.bigint(), it should do what you are looking for.

We will validate our input using client-side zod. Zod handles TypeScript-first schema validation with static type inference. This means that it will not only validate your fields, it will also set types on validated fields.

A word of warning: while discriminated unions are very powerful, there's an ongoing discussion on whether discriminated unions should be deprecated and replaced with a different API.

I was first introduced to Zod by Adam Bobrow - a colleague of mine and a dear friend. Adam was sick and tired from JavaScript's brittleness, and about two years ago he started migrating our code base to TypeScript. But that wasn't enough for him. He kept complaining: "What good are my types, if some other service decides to send me bad data and breaks my code?". That's when he discovered Zod.