ts-protoc-gen VS graphql-error-handling-with-union-and-fpts

Compare ts-protoc-gen vs graphql-error-handling-with-union-and-fpts and see what are their differences.

Our great sponsors
  • SurveyJS - Open-Source JSON Form Builder to Create Dynamic Forms Right in Your App
  • WorkOS - The modern identity platform for B2B SaaS
  • InfluxDB - Power Real-Time Data Analytics at Scale
ts-protoc-gen graphql-error-handling-with-union-and-fpts
2 1
1,325 13
0.5% -
2.9 4.2
3 months ago 9 months ago
TypeScript TypeScript
Apache License 2.0 -
The number of mentions indicates the total number of mentions that we've tracked plus the number of user suggested alternatives.
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.

ts-protoc-gen

Posts with mentions or reviews of ts-protoc-gen. We have used some of these posts to build our list of alternatives and similar projects. The last one was on 2022-03-27.
  • Creating type definition from protocol buffer
    2 projects | /r/typescript | 27 Mar 2022
  • GraphQL error handling to the max with Typescript, codegen and fp-ts
    11 projects | dev.to | 7 Mar 2022
    :::note When using remote APIs, we often have the possibility to generate the types automatically from a JSON schema for REST APIs, from protobuf files for gRPC-based APIs, from a database schema, etc. You might even be using an external API through an SDK that already provides you with all types. In such cases, the creation of specialized Error classes is not mandatory. However, it might still be a good idea to do so to provide application-specific errors rather than bubbling up 3rd-party low-level errors. For such cases, the upcoming Ecma TC39 proposal for Error Cause is useful as it allows to chain errors. Polyfills exist: Pony Cause or error-cause. :::

graphql-error-handling-with-union-and-fpts

Posts with mentions or reviews of graphql-error-handling-with-union-and-fpts. We have used some of these posts to build our list of alternatives and similar projects. The last one was on 2022-03-07.

What are some alternatives?

When comparing ts-protoc-gen and graphql-error-handling-with-union-and-fpts you can also consider the following projects:

protobuf-ts - Protobuf and RPC for TypeScript

monio - The most powerful IO monad implementation in JS, possibly in any language!

effect - A fully-fledged functional effect system for TypeScript with a rich standard library

schemats - Generate typescript interface definitions from SQL database schema

graphql-yoga - 🧘 Rewrite of a fully-featured GraphQL Server with focus on easy setup, performance & great developer experience. The core of Yoga implements WHATWG Fetch API and can run/deploy on any JS environment.

fp-ts - Functional programming in TypeScript

Stack - Tech Stack developed by The Guild

graphql-spec - GraphQL is a query language and execution engine tied to any backend service.

pony-cause - Ponyfill and helpers for the standardized Error Causes

zenum - A better enum for simplicity and typesafety.