JSON Schema to TypeScript in Fastify
What you'll learn: How to automatically derive TypeScript types from JSON schemas in Fastify using schema inference tools.
The Schema-First Problem in Fastify
You've already learned that Fastify uses generics for request and reply typing. But manually writing both JSON schemas (for validation) and TypeScript types (for type safety) creates duplication. Change a schema? Update the type. Change the type? Update the schema. This is error-prone.
Fastify's schema property accepts JSON Schema objects for validation. The challenge: how do you make TypeScript understand those schemas as types?
Two Main Solutions
1. json-schema-to-ts
This library converts JSON Schema objects into TypeScript types at compile time using as const and type-level magic.
2. @fastify/type-provider-typebox
TypeBox lets you define schemas with TypeScript-first syntax, then use them as both runtime validators and compile-time types. The type provider bridges TypeBox schemas to Fastify's generics.
How They Work
Both approaches leverage the schema you already write for validation to automatically infer the TypeScript types for your route. You define the shape once, and get both runtime validation and compile-time type safety.
With json-schema-to-ts, you write standard JSON Schema with as const, then use FromSchema to extract types.
With TypeBox, you use Type.Object() and similar builders, which are both schemas and types simultaneously.
Why This Matters
This pattern eliminates the dual-maintenance problem. Your schema is the single source of truth. TypeScript types flow automatically from it, ensuring validation rules and type constraints never drift apart.
Key Takeaway: Fastify's schema property can drive TypeScript inference using json-schema-to-ts or @fastify/type-provider-typebox, eliminating duplicate type definitions and keeping validation in sync with types.