taxonomy
zod
taxonomy | zod | |
---|---|---|
40 | 294 | |
17,765 | 31,015 | |
2.7% | - | |
0.0 | 9.3 | |
3 days 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.
taxonomy
-
T3 stack with app router and supabase
I am building this app with inspiration from Taxonomy and Acme corp so a lot of the design comes from there.
-
5 Github Repositories To Master Next.js 😎
View on GitHub
-
Navigating Uncharted Waters: Building the MVP and Finding the Right Audience (Part 2)
Now, I must confess that I'm primarily a back-end engineer, and crafting a beautiful front-end was, well, a bit of an adventure. To keep things straightforward, I opted for simplicity. I figured I could enhance it as my customer base grew, as the real value, of course, lies in the robustness of the API and its backend. Looking back, I might consider using a template like https://tx.shadcn.com/ if I were to start all over again. It appears to be a great starting point for any SaaS, but the setup might pose some challenges.
-
Nextjs beginner
Check out these two GitHub repositories: https://github.com/sadmann7/skateshop/ and https://github.com/shadcn/taxonomy/. They both use Next.js 13 and have well-structured folders and well-written code. Next.js provides performance optimization. To improve it further, avoid loading unnecessary items and use a CDN for fast content delivery. Both not loading unnecessary content & lazy loading) and CDN is 2 individual topics to dive into.
-
Migrating from Next Auth and Prisma to Supabase for a Stripe Integration - Thoughts?
I've also been inspired by this repo, but the Vercel template seems more achievable for me at this point.
-
Integrating Stripe Functionality from an Existing Next.js Repo into My Own Application
In addition to the repository I mentioned in my original post, I've also been inspired by another repository (Taxonomy Repo) which has implemented a similar Stripe integration. However, this one is a bit more complex and I'm finding the Vercel template to be more achievable for my current skill level.
-
Need Help with Stripe Webhook Integration in Next.js App Using App Router
I'm currently working on a Next.js project where I'm trying to integrate Stripe for payments and webhooks. I've been following the Taxonomy GitHub repo for guidance, particularly for setting up the app router and the lib files.
- How to take my React knowledge to the next level?
- App Router example repos
- Tailwind in Large Enterprise Projects
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?
FormalGrammars - Context-free and linear grammars in Haskell (parsing, pretty-printing, embedded DSL)
class-validator - Decorator-based property validation for classes.
dub - Open-source link management infrastructure.
joi - The most powerful data validation library for JS [Moved to: https://github.com/sideway/joi]
TaxonomyTools - Tools to process and visualize NCBI taxonomy data
typebox - Json Schema Type Builder with Static Type Resolution for TypeScript
bioinformatics-toolkit - A collection of bioinformatics algorithms
Yup - Dead simple Object schema validation
hPDB - PDB parser in Haskell
ajv - The fastest JSON schema Validator. Supports JSON Schema draft-04/06/07/2019-09/2020-12 and JSON Type Definition (RFC8927)
ts-faker - Generate fake data using TypeScript interfaces
io-ts - Runtime type system for IO decoding/encoding