telefunc VS phero

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

That's one of the reasons that drove me to create Phero: https://phero.dev

I’m one of the authors of Phero. It’s goal is similar to tRPC: fullstack typesafety between servers and clients.

One difference is syntax: Phero leverages the TS compiler api to generate parsers for your backend functions. It will parse input and output or your api, 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: you could also use https://phero.dev

Long story short: when fetching data, you should be validating the data, before casting it to a type you’re expecting it to be. There are a lot of different approaches for this, but being the go-author my favorite would be Phero (https://phero.dev). With this, you can build your API in typescript as well, automatically generate a client for your frontend to call the API. Phero will make sure all data is correct in runtime, automatically.

For those looking for an alternative: Definitely check out https://phero.dev. As the co-creator I’m totally biased of course, but thanks to its build-step IDE-performance is great 😊👍

What about Phero? https://phero.dev

Can we add Phero to the list? :) https://github.com/phero-hq/phero

You can use Phero. You can use it on your backend and frontend. It basically created a typed API from your backend afaik