telefunc VS trpc

Compared with tRPC: https://github.com/brillout/telefunc/issues/9

For JavaScript based projects TeleFunc[1] can make development way simpler by 'removing' the need for an API.

[1]: https://telefunc.com/

- api routes (cloud functions) require another package (on purpose). see https://telefunc.com/ from the same maintainer

other than that, no gatchas i encountered. i would choose vite-plugin-ssr again.

Another suggestion to solve your problem could be to use telefunc

> My experience was that for the simplest use cases, the ergonomics were unbeatable.

Exactly.

> the “just a function” interface was a distraction and I found myself wishing for a more conventional RPC interface.

For real-time use cases, I agree. I believe functions are the wrong abstraction here for real-time. I do plan to support real-time but using a "it's just variables" abstraction instead, see https://github.com/brillout/telefunc/issues/36.

> cleverer abstractions usually mean more work overall to integrate everything and boring is better.

Yes, Telefunc's downside is that it requires a transformer. The Vite and Webpack one are reliable and used in production (using `es-module-lexer` under the hood). The hope here is that, as Telefunc's popularity grows, more and more stacks are reliably supported. Also, there is a prototype using Telefunc without a transformer at all, which works but needs polishing.

> I experimented with a higher-magic version of this a couple of years ago.

Neat, curious, is it on GitHub?

An alternativeto tRPC that I find easier to use is telefunc

RESTful API: RESTful API does not have machine-readable metadata cacheable, and query validation is not available.(There are some libraraies tried to solve this issue like TRPC)

tRPC + Cloudflare Workers Example

Hi I'm working with trpc + nextjs app dir (unsupported by trpc currently) and trpc context

I'm using TRPC with Next13 App directory and I can't manage to invalidate queries. Seing from their example there is a way to do it https://github.com/trpc/trpc/blob/96956e790e6862bcc6dcc4622edc8e48da0adbcb/examples/.experimental/next-app-dir/src/app/post-example/page.tsx

It is. But RSC make many library authors and maintainers question whether their library is still needed in a RSC world and if so how they can support it. Same story with tRPC https://github.com/trpc/trpc/issues/3297

Also, while trying to debug this, and this is way outside my league but I noticed this: Is there possibly an error in the Updater TS-definitions in https://github.com/trpc/trpc/blob/main/packages/react-query/src/shared/proxy/utilsProxy.ts at lines 155+156 & 167+168 because they are duplicate-lines and seems to be where my issues are coming from.

Unfortunately, tRPC and NestJs do not play well together by default, and the tRPC team does not intend to integrate the two through an official plugin for the time being.

- https://github.com/trpc/trpc: End-to-end typesafe APIs made easy. Never write another API contract again.