ts-protoc-gen
pony-cause
Our great sponsors
ts-protoc-gen | pony-cause | |
---|---|---|
2 | 4 | |
1,325 | 48 | |
0.5% | - | |
2.9 | 5.4 | |
3 months ago | 6 days ago | |
TypeScript | JavaScript | |
Apache License 2.0 | BSD Zero Clause 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.
ts-protoc-gen
- Creating type definition from protocol buffer
-
GraphQL error handling to the max with Typescript, codegen and fp-ts
:::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. :::
pony-cause
-
GraphQL error handling to the max with Typescript, codegen and fp-ts
:::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. :::
-
Error cause: a new feature in JS that can help a lot with debugging
What a coincidence I just started using this in a project yesterday! I'm using pony-cause as a polyfill since I'm on node 15
-
TypeScript 4.5 adds JSDoc template tag defaults
I will push this new code to my pony-cause module very soon, just wanted to write this up first 🥳
-
Pony Cause 1.0: Error Causes
The impact and cause provides the most value when paired with the other, and that's what Error Cause enables and what Pony Cause is is a ponyfill for and provides helpers for.
What are some alternatives?
protobuf-ts - Protobuf and RPC for TypeScript
proposal-error-cause - TC39 proposal for accumulating errors
graphql-error-handling-with-union-and-fpts
TypeScript - TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
effect - A fully-fledged functional effect system for TypeScript with a rich standard library
types-in-js - Tips and tricks for working with types in JavaScript
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.
Stack - Tech Stack developed by The Guild
fp-ts - Functional programming in TypeScript
zenum - A better enum for simplicity and typesafety.
type-coverage - A CLI tool to check type coverage for typescript code