zod
trpc
zod | trpc | |
---|---|---|
290 | 35 | |
30,477 | 32,748 | |
- | 1.3% | |
9.1 | 9.8 | |
3 days ago | 2 days 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.
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.
trpc
-
Key differences between GraphQL and RESTful API
RESTful API: RESTful API does not have machine-readable metadata cacheable, and query validation is not available.(There are some libraraies tried to solve this issue like TRPC)
-
Implementing Authorization with Clerk in a tRPC app running on a Cloudflare Worker
tRPC + Cloudflare Workers Example
- how to improve UX of checking changes in ONE file though git history
-
trpc + nextjs app dir + fetchRequestHandler
Hi I'm working with trpc + nextjs app dir (unsupported by trpc currently) and trpc context
-
TRPC invalidation app directory
I'm using TRPC with Next13 App directory and I can't manage to invalidate queries. Seing from their example there is a way to do it https://github.com/trpc/trpc/blob/96956e790e6862bcc6dcc4622edc8e48da0adbcb/examples/.experimental/next-app-dir/src/app/post-example/page.tsx
-
tRPC β Move Fast and Break Nothing. End-to-end typesafe APIs made easy
It is. But RSC make many library authors and maintainers question whether their library is still needed in a RSC world and if so how they can support it. Same story with tRPC https://github.com/trpc/trpc/issues/3297
-
trpc VS prim-rpc - a user suggested alternative
2 projects | 23 Jul 2023
-
T3\tRPC - How do you change the cache?
Also, while trying to debug this, and this is way outside my league but I noticed this: Is there possibly an error in the Updater TS-definitions in https://github.com/trpc/trpc/blob/main/packages/react-query/src/shared/proxy/utilsProxy.ts at lines 155+156 & 167+168 because they are duplicate-lines and seems to be where my issues are coming from.
-
SPARTAN. Type-safe Angular full-stack development powered by Analog.
Unfortunately, tRPC and NestJs do not play well together by default, and the tRPC team does not intend to integrate the two through an official plugin for the time being.
-
GitHub Accelerator: our first cohort and what's next
- https://github.com/trpc/trpc: End-to-end typesafe APIs made easy. Never write another API contract again.
What are some alternatives?
class-validator - Decorator-based property validation for classes.
Nest - A progressive Node.js framework for building efficient, scalable, and enterprise-grade server-side applications with TypeScript/JavaScript π
joi - The most powerful data validation library for JS [Moved to: https://github.com/sideway/joi]
domain-functions - Decouple your business logic from your framework. With first-class type inference from end to end. [Moved to: https://github.com/seasonedcc/domain-functions]
typebox - Json Schema Type Builder with Static Type Resolution for TypeScript
graphql-zeus - GraphQL client and GraphQL code generator with GraphQL autocomplete library generation β‘β‘β‘ for browser,nodejs and react native ( apollo compatible )
Yup - Dead simple Object schema validation
denodb - MySQL, SQLite, MariaDB, PostgreSQL and MongoDB ORM for Deno
ajv - The fastest JSON schema Validator. Supports JSON Schema draft-04/06/07/2019-09/2020-12 and JSON Type Definition (RFC8927)
MySQL - A pure node.js JavaScript Client implementing the MySQL protocol.
io-ts - Runtime type system for IO decoding/encoding
strapi-mongo-next - NextJs frontend, Strapi backend API, and MongoDb. A full-stack sample business website styled with the latest Material-Ui.