ditsmod VS ajv

My last measurements were when Fastify was v3.25, Restify v8.6 and Ditsmod v2.0. From that moment on, although Fastify remained in the lead, other frameworks came quite close to its results.

For those users who see this as a problem and want the framework they use to support this feature, I can recommend Ditsmod. This framework solves this issue as follows.

Good application modularity is closely related to the injector tree hierarchy that Dependency Injection (DI) creates. DI injectors are sometimes referred to as DI containers, but since NestJS and Ditsmod have taken many concepts from Angular, this post will use the term "injectors" (since it does in Angular).

This post compares NestJS v9.2.0 and Ditsmod v2.27.0. A finished example of validation with the Ditsmod application can be viewed at github. I am the author of Ditsmod.

A finished example from @ditsmod/cors can be viewed in the Ditsmod repository.

You can view the code with examples of the use of @ditsmod/i18n in the Ditsmod repository, although it is more convenient to view it locally, so it is better to clone it first:

Thanks to the system of extensions, Ditsmod applications are more expressive and with less code. For example, if you compare OpenAPI modules written in Ditsmod and NestJS, the Ditsmod module is 3.5 times smaller in the number of lines of code or the number of files.

Ditsmod є Node.js веб-фреймворком, його назва складається із DI + TS + Mod, щоб підкреслити важливі складові: він має Dependency Injection, написаний на Type*Script, та спроектований для хорошої **Mod*ularity (тобто модульності).

Ajv’s documentation is available here.

In the JavaScript ecosystem you can use the excellent AJV package to validate any JavaScript object against a JSON schema. This is especially useful to ensure that API contracts are maintained when communicating with other services.

Since Fastify supports schema validation with Ajv, the validate module is no longer required on the /shorten route, and we can specify the JSON schema directly on the route. The controllers for both routes will largely remain the same, except that the res parameter is renamed to reply as before:

There's a ton of schema validators out there and most devs have their personal favorite. Mine was zod and is now typebox + ajv.

Good validator library: https://www.npmjs.com/package/ajv

Fastify uses JSON schema to define the validation rules for each route's input payload, which includes the request body, query string, parameters, and headers. The JSON schema is a standard format for defining the structure and constraints of JSON data, and Fastify uses Ajv, one of the fastest and most efficient JSON schema validators available.

In Fastify, JSON schema validation is a built-in feature that allows you to validate the payload of incoming requests before the handler function is executed. This ensures that incoming data is in the expected format and meets the required criteria for your business logic. Fastify's JSON schema validation is powered by the Ajv library, a fast and efficient JSON schema validator.

I think you're looking for a json schema validator like Ajv or Zod.

We can use JSON Schema to validate that our data adheres to a specific structure. Ajv is one popular validator tool for JavaScript applications that allows us to create a schema and then validate JSON against that schema. Here's an example of using Ajv to validate one of the above JSON examples against a schema:

Hey HN,

We're designing a new system and have been kicking the can about JSON object definitions and validation. Soon we need to settle on a system to validate API request bodies and provide helpful error messages.

In the past, I've used JSON Schema ( https://json-schema.org/ ) to define definitions and ajv ( https://ajv.js.org/ ) to validate, but it's a bit verbose and ajv validation errors are more cryptic than I'd like to deal with.

TypeSchema looks interesting. It seems solid (and perhaps stable?), but development hasn't been active for 2 years. It also looks like we'd still need to generate JSON Schema and choose a validation library

Anyway, I'm very curious how others are approaching this problem. How do you organize and generate validations for your type definitions? What libraries do you use to validate and provide human readable error messages?

Thank you!