phero

Shameless plug: I’m one of the authors of Phero [1]. It’s goal is similar to tRPC: fullstack typesafety between your server and client(s). One difference is syntax: Phero leverages the TS compiler api to generate parsers for your backend functions. It will parse input and output of your api functions, automatically, based on the types you define for your functions. It will generate a declaration file of your api and generate an RPC style client SDK for your frontend. Another difference is that it aims to be more batteries includes. [1] https://github.com/phero-hq/phero Comparison: https://phero.dev/docs/comparisons/tRPC

Shameless plug to my project Phero [0]. It’s a bit like gRPC but specifically for full stack TypeScript projects. It has a minimal API, literally one function, with which you can expose your server’s functions. It will generate a Typesafe SDK for your frontend(s), packed with all models you’re using. It will also generate a server which will automatically validate input & output to your server. One thing I’ve seen no other similar solution do is the way we do error handling: throw an error on the server and catch it on the client as if it was a local error. As I said, it’s only meant for teams who have full stack TypeScript. For teams with polyglot stacks an intermediate like protobuf or GraphQL might make more sense. We generate a TS declaration file instead. [0] https://github.com/phero-hq/phero

Whoa, that’s so similar to our project [1] it’s almost scary :) How are errors handled though? What happens when you “throw Abort()”. https://github.com/samen-io/samen