joi VS zod

Package Feature Merit Demerit Link Zod TypeScript-first schema validation with static type inference Method chaining and easy to get ts type Newer package zod.dev joi This is almost same to zod Have many plugins Doesn't support static type inference https://github.com/sideway/joi Yup This is almost same to zod Have many plugins Missing some feature, function, deep object, promise... ... https://github.com/jquense/yup class-validator Validate class properties Have many features Code isn't clean https://github.com/typestack/class-validator ajv Validate by json scheme Enable to share schem to other languages Not supported typescript https://ajv.js.org/

Using Joi, a data validator for JavaScript.

See how I've used joi for validating the request body. You can install and use different libraries like this inside the helpers/routes. Joi can be installed with the following command:

3. joi

⭐ Recommended: Doing this manually is a ton of work, and if you're dealing with unknown objects often it would be better to lean onto a validation library to simplify it. My personal favorite is superstruct, although lots of people like joi or zod. They all do the same thing

The class-validator / class-transform looks really nice for formatting/validation but there is also joi. suretype is attractive since theoretically typeconv could generate jsonSchema for json-schema-faker and Open API docs.

Since Typescript is just a language and not a library of some sorts, it doesn't add runtime functionality. If this is what you're after, there's so many libraries that help converting unknown's into known types - joi, yup, superstruct (my choice), purify-ts Codec, io-ts

What does this library provide that is not provided by Yup, Zod, Superstruct (a personal favorite), Joi, Nope, computed-types, typanion, and all the other validation libraries?

True, I remember there's Yup and joi for JavaScript

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.