effect
ts-protoc-gen
Our great sponsors
| effect | ts-protoc-gen | |
|---|---|---|
| 25 | 2 | |
| 4,657 | 1,325 | |
| 25.2% | 0.5% | |
| 9.9 | 2.9 | |
| 2 days ago | 3 months ago | |
| TypeScript | TypeScript | |
| MIT License | Apache License 2.0 |
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.
effect
-
Exploring Effect, a meta-state RxJS-like framework
Effect is a functional library for building and composing asynchronous, concurrent, and reactive programs in TypeScript. It focuses on providing a robust and type-safe way to manage side effects in your programs.
-
A better way to handle errors in JavaScript
Just use a library that already contains this and more functional programming idioms, like fp-ts or its successor, Effect [0]. It is a little more complex to learn but much more robust that simply implementing your own Result and other types.
[0] https://www.effect.website/
- opinions about Effect-TS, do you recommend using it? when to use it? When to avoid it? not worth it?
-
Building React Components Using Unions in TypeScript
effect-ts
- Effect - A set of libraries to write better TypeScript
- Effect – A set of libraries to write better TypeScript
- Effect-ts: a library for writing ZIO-like effect-based applications
- Effect, a functional effect system for TypeScript with a rich standard library
- Effect: A functional effect system for TypeScript with a rich standard library
- Alternatives to scala FP
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. :::
What are some alternatives?
fp-ts - Functional programming in TypeScript
protobuf-ts - Protobuf and RPC for TypeScript
pratica - 🥃 Functional Algebraic Data Types
graphql-error-handling-with-union-and-fpts
tyrian - Elm-inspired Scala UI library.
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.
contentlayer - Contentlayer turns your content into data - making it super easy to import MD(X) and CMS content in your app
Stack - Tech Stack developed by The Guild
eslint-plugin-functional - ESLint rules to disable mutation and promote fp in JavaScript and TypeScript.
pony-cause - Ponyfill and helpers for the standardized Error Causes
Index - ⚡ Pattern Matching in Typescript
zenum - A better enum for simplicity and typesafety.