runtypes
zod
runtypes | zod | |
---|---|---|
22 | 290 | |
2,548 | 30,630 | |
0.3% | - | |
5.6 | 9.1 | |
3 months ago | 1 day ago | |
TypeScript | TypeScript | |
MIT License | MIT License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
runtypes
-
When should I use runtime checks (and which runtime checker should I use)?
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'.
-
An almost religious case for Rust
Runtypes would probably be a better example.
-
'The best thing we can do today to JavaScript is to retire it’ Douglas Crockford
this has been solved by several packages, runtypes https://github.com/pelotom/runtypes being my favorite
-
How to force a type when importing a JSON file?
I personally like https://github.com/pelotom/runtypes because it bundles your Schema Info and the corresponding Typescript types
- Why doesn’t TypeScript natively do any type checking
-
Create d.ts for API response
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.
-
Typing for JSON Payloads
Also runtypes and (as mentioned below) zod.
-
How to check that an 'unknown' object has a specific key and that the key is a specific type?
Seconding the recommendation to use a library for this. runtypes and io-ts are two other alternatives.
-
Check types at the top level or in each function?
I wouldn't reinvent the wheel: https://github.com/pelotom/runtypes
-
Minimal and fast runtime API payload sanitiser and error message handling
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
-
Simplifying Form Validation with Zod and React Hook Form
[Zod Documentation](https://zod.dev/) [Zod Error Handling](https://zod.dev/ERROR_HANDLING?id=error-handling-in-zod) [React-Hook-Form Documentation](https://react-hook-form.com/get-started) [Hookform Resolvers](https://www.npmjs.com/package/@hookform/resolvers)
-
Figma's Journey to TypeScript
This is a very fair comment, and you seem open to understanding why types are useful.
"problems that are due to typing" is a very difficult thing to unpack because types can mean _so_ many things.
Static types are absolutely useless (and, really, a net negative) if you're not using them well.
Types don't help if you don't spend the time modeling with the type system. You can use the type system to your advantage to prevent invalid states from being represented _at all_.
As an example, consider a music player that keeps track of the current song and the current position in the song.
If you model this naively you might do something like: https://gist.github.com/shepherdjerred/d0f57c99bfd69cf9eada4...
In the example above you _are_ using types. It might not be obvious that some of these issues can be solved with stronger types, that is, you might say that "You rarely see problems that are due to typing".
Here's an example where the type system can give you a lot more safety: https://gist.github.com/shepherdjerred/0976bc9d86f0a19a75757...
You'll notice that this kind of safety is pretty limited. If you're going to write a music app, you'll probably need API calls, local storage, URL routes, etc.
TypeScript's typechecking ends at the "boundaries" of the type system, e.g. it cannot automatically typecheck your fetch or localStorage calls return the correct types. If you're casting, you're bypassing the type systems and making it worthless. Runtime type checking libraries like Zod [0] can take care of this for you and are able to typecheck at the boundaries of your app so that the type system can work _extremely_ well.
[0]: https://zod.dev/ note: I mentioned Zod because I like it. There are _many_ similar libraries.
-
From Flaky to Flawless: Angular API Response Management with Zod
Zod is an open-source schema declaration and validation library that emphasizes TypeScript. It can refer to any data type, from simple to complex. Zod eliminates duplicative type declarations by inferring static TypeScript types and allows easy composition of complex data structures from simpler ones. It has no dependencies, is compatible with Node.js and modern browsers, and has a concise, chainable interface. Zod is lightweight (8kb when zipped), immutable, with methods returning new instances. It encourages parsing over validation and is not limited to TypeScript but works well with JavaScript as well.
- TypeScript Essentials: Distinguishing Types with Branding
-
You can’t run away from runtime errors using TypeScript
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.
-
Best Next.js Libraries and Tools in 2024
Link: https://zod.dev/
-
Popular Libraries For Building Type-safe Web Application APIs
You can check out their documentation here.
-
Epic Next JS 14 Tutorial Part 4: How To Handle Login And Authentication in Next.js
You can learn more about Zod on their website here.
-
What even is a JSON number?
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.
-
Error handling in our form component for the NextAuth CredentialsProvider
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.
What are some alternatives?
typescript-is
class-validator - Decorator-based property validation for classes.
io-ts - Runtime type system for IO decoding/encoding
joi - The most powerful data validation library for JS [Moved to: https://github.com/sideway/joi]
type-fest - A collection of essential TypeScript types
typebox - Json Schema Type Builder with Static Type Resolution for TypeScript
typegraphql-prisma - Prisma generator to emit TypeGraphQL types and CRUD resolvers from your Prisma schema
Yup - Dead simple Object schema validation
ts-auto-guard - Generate type guard functions from TypeScript interfaces
ajv - The fastest JSON schema Validator. Supports JSON Schema draft-04/06/07/2019-09/2020-12 and JSON Type Definition (RFC8927)
nest-clean-architecture - 🏛️ Nest.js clean architecture example following some DDD principles with use-cases written in functionnal programming.