xod VS zod

By leveraging Zod for your form validation you are able to use the same type-definitions to validate your application’s data on the front-end and the back-end — saving you time and reducing the opportunities for malformed data to find its way into your database.

I made a Sveltekit Auth starter if anyone needs a starting point for an app. A demo is here. It is an open source auth starter project utilizing Lucia for authentication, Skeleton for ui elements, Prisma for database connectivity and type safety and Sveltekit for the javascript framework. I also used Zod and Superforms to handle form validation and management. It has email verification, password reset, and will send an email if the user changes their email address to re-verify it. It is released as open source under an MIT license.

This is easily solved using Zod. Zod is a literal godsend, and TypeScript is what makes it so useful. Parsing JSON with pure JS is very type-dangerous, while with Zod & TS it becomes very type-safe.

TypeScript doesn't perform runtime type checking, for that you'd want to use something like zod

Note how we’re using Zod as a built-in JSON schema validation tool.

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

src/utils/validateInput.ts: an Express.js middleware wrapper that makes use of zod to validate request body payloads to the API endpoints.

I use zod to ensure that the typing can be trusted and derive my types from it. Finally, I generate test data using zod-mock. It works great.

On the server, you create a tRPC API by defining your procedures. Procedures are the composable functions used to build your backend. They're composable and can be queries, mutations, or subscriptions. Routers contain multiple procedures. Often, we use a the popular Zod validator library to ensure the input from the client has exactly the shape that our procedure expects. Finally, we always export the type of our API's tRPC router so we can use it in our frontend code.

In combination with the awesome zod library we created a special constructor for strings with fixed length. It can be used both on the back end for incoming requests validation, but also on the front end for forms validation.