runtypes VS zod

In terms of which runtime checker I should use. The first tutorial I saw suggested 'Zod', doing a bit more searchign yielded other options such as 'runtypes'.

Runtypes would probably be a better example.

this has been solved by several packages, runtypes https://github.com/pelotom/runtypes being my favorite

I personally like https://github.com/pelotom/runtypes because it bundles your Schema Info and the corresponding Typescript types

When I have to deal with data from API calls, I usually use a runtime typing library like Runtypes or Zod to check the responses at the boundary. These libraries can automatically give you TS types (using their static or infer utilities) to use throughout the rest of the project.

Also runtypes and (as mentioned below) zod.

Seconding the recommendation to use a library for this. runtypes and io-ts are two other alternatives.

I wouldn't reinvent the wheel: https://github.com/pelotom/runtypes

What does your library provide that others don't? For example: https://github.com/colinhacks/zodhttps://github.com/hapijs/joihttps://github.com/jquense/yuphttps://github.com/gcanti/io-tshttps://github.com/pelotom/runtypeshttps://github.com/sindresorhus/ow

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.

It is (or should be) common practice to parse/validate any external data you depend on. You should be doing this for Javascript too. I find that the library https://zod.dev/ is quite helpful for this

Astro uses Zod, a Typescript-first schema validation library, to type-check the collections' schemas. It helps validate data types when using collections inside UI components.