json-schema-to-ts VS fastify-type-provider-typebox

JSON Schema To TS

// First create a general "post" schema // Shared Schema export const postSchema = { $id: 'post', type: 'object', properties: { id: { type: 'number' }, title: { type: 'string' }, published: { type: 'boolean' }, content: { type: 'string' }, tags: { type: 'array', items: { type: 'string' } }, deleted: { type: 'boolean' } }, required: ['title', 'published', 'content', 'tags', 'deleted'] } as const // We don't need to create a separate "bodySchema". // But directly infer type from postSchema export type Body = FromSchema // Reply Schema // Check https://www.fastify.io/docs/latest/Reference/Validation-and-Serialization/#adding-a-shared-schema const replySchema = { type: 'object', properties: { posts: { type: 'array', items: { $ref: 'post#' } } }, additionalProperties: false } as const // Check https://github.com/ThomasAribart/json-schema-to-ts#references export type Reply = FromSchema< typeof replySchema, { references: [typeof postSchema] } > // Also make ReplyNotFound reusable for future use export const postNotFoundSchema = { $id: 'postNotFound', // add $id here type: 'object', required: ['error'], properties: { error: { type: 'string' } }, additionalProperties: false } as const export type PostNotFound = FromSchema

json-schema-to-ts comes to the rescue. 💪

https://github.com/ThomasAribart/json-schema-to-ts - Infers TS Types from raw JSON Schema object literals you embed in your code.

Fonte: https://github.com/ThomasAribart/json-schema-to-ts

My experience is that it's fine(tm). "JavaScript on server-side" does not bother me; V8 owns bones. None of my debugging output includes JS lines because I pack source maps, which TypeScript happily includes.

Multi-threading isn't complex, because there isn't multi-threading. There's coprocessing via Promises, and there indeed are a lot of Node developers who think you don't need locking functionality because it's not multi-threaded (there was an absolutely bonkers discussion a few years ago where a JS developer insisted you didn't need locks), but whatever, they think that about other languages too, use async-lock or whatever.

"Maturity" is a word that means different things to different people. There is not a consensus-best-choice framework like Spring Boot in Node. But the tools are there and they're excellent (Python is similar, FWIW--FastAPI is the closest thing to a right answer that I think I've ever used, I wish I liked Python more because that owns). Fastify is perhaps The Best web framework I've ever used, and it has only gotten better with v4 allowing you to engage with type providers to create an end-to-end, automatically typechecked route declaration framework. It lets you do stuff like this, where you specify a request schema as JSON Schema (encoded via typebox) and it'll statically derive the TypeScript type for you whilst also using it for request schema validation:

https://github.com/fastify/fastify-type-provider-typebox#exa...

The tools are there. You do have to wire them together. There's value in that, for the way I write code and the stuff I enjoy building.

Overall, I'll trade some compilation niceties and even some (but to be frank, not much) performance for a vastly better language in day-to-day use. I really like the JVM. I've been using it professionally for twelve years. I also like the CLR. I did Google Summer of Code for the Mono Project in 2008, I've been around. But the day-to-day of writing code in the dominant languages on those platforms for things other than CRUD does frustrate me, and the difficulty of using the type system to effectively encode intent makes it much harder for me to write software that can guide other people to not misuse it.

(If I ever wrote something at extragalactic scale, yeah, sure, whatever, I'd rewrite hot paths in something else. But I absolutely don't care about that.)

Checkout https://github.com/fastify/fastify-type-provider-typebox or https://github.com/fastify/fastify-type-provider-json-schema-to-ts for a better TS experience also.