vee-validate VS validator.js

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?

To keep the focus of this guide on building our chat app, I'll skip the steps in setting up certain dependencies, such as Tailwind CSS for styling, Nano ID for generating strings used to create a short URL version of an original URL and validator for implement URL validation.

express-validator is a set of express.js middlewares that wraps validator.js validator and sanitizer functions.

For emails, a robust email validator from a well maintained package such as validator would be a good idea.

Regarding escaping brackets and ampersands - would you do this prior to storing the value in the DB? This would seem like the only way to do it, otherwise you are looking at escaping after DB queries or escaping in the client, neither of which I like. React automatically escapes strings but it's not something I want to leave to chance, and I do not want "dangerous" data in storage. validatorjs's escape() function would seem the best fit for the job.

Sorry, are you referring to this https://github.com/validatorjs/validator.js as a wrapper

+1 for lodash! It's like a superpower once you realize everything it can do. Another good one is validator.js.

I'm taking a Javascript course at the moment, and while it's truly fantastic, parts of the Mongo stuff could use some updating (already had to course correct with some syntax). I'm now getting an error I really don't know what to do with, and SO isn't helping in this case. Per the course, we're using validator (https://www.npmjs.com/package/validator). Most relevant code file:

emailIsValid uses the helper method isEmail from the validator package to assert that the provided email is a valid email format