6 ms·
ts-rest doesn't see a lot of support these days. It's lack of adoption of modern tanstack query integration patterns finally drove us look for alternatives. Lu
by hmcdona1 1y ago
ts-rest doesn't see a lot of support these days. It's lack of adoption of modern tanstack query integration patterns finally drove us look for alternatives.
Luckily, oRPC had progressed enough to be viable now. I cannot recommend it over ts-rest enough. It's essentially tRPC but with support for ts-rest style contracts that enable standard OpenAPI REST endpoints.
- https://orpc.unnoq.com/ https://orpc.unnoq.com/
- https://github.com/unnoq/orpc https://github.com/unnoq/orpc
- bavell 1y agoFirst time hearing about oRPC, never heard of or used ts-rest and I'm a big fan of tRPC. Is the switch worth the time and energy?
- hmcdona1 1y agoIf you're happy with tRPC and don't need proper REST functionality it might not be worth it. However, if you want to lean that direction where it is a helpful addition they recently added some tRPC integrations that actually let you add oRPC alongside an existing tRPC setup so you can do so or support a longer term migration. - https://orpc.unnoq.com/docs/openapi/integrations/trpc https://orpc.unnoq.com/docs/openapi/integrations/trpc