|
|
|
|
|
by kamilafsar
1189 days ago
|
|
Yes, Phero has a build step. Phero does come with a CLI and will watch code changes, build your TS alongside with an client SDK. In our experience the latency between changing something in your API, and seeing compile errors arise in the client is just a few seconds. And this only matters when your API contract changes, which is of course not always. Not a biggy in our eyes. In order to run, you'd need to compile TS anyways. :) In our opinion this is well worth the "magic" Phero adds: it will work with plain TS. No "t.string" like apis to build your apis/models. Matter of taste I guess :) |
|
We've "had" end-to-end typesafety with codegen tools openapi/swagger and graphql etc.
However, the big issue with a lot of those tools is that you end up having to manage this compile step.
The real magic of trpc is exactly this point about it being without a compiler, where the types are derived from the very same typescript files - this is what gives it this immediacy and feeling of it being instant and not having to deal with a compile step.
I've always wondered whether we'd get the same benefits and niceties with a really streamlined compiling approach - perhaps something like phero. But it's just a little harder of a sell compared to the built-in typesafety you get from trpc