| zact | telefunc | |
|---|---|---|
| 4 | 12 | |
| 1,028 | 617 | |
| - | - | |
| 10.0 | 9.1 | |
| 8 months ago | 7 days ago | |
| TypeScript | TypeScript | |
| MIT License | MIT License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
zact
-
tRPC – Move Fast and Break Nothing. End-to-end typesafe APIs made easy
You can use zact for that
https://github.com/pingdotgg/zact
- Strongly-typed API using NextJS App Dir?
-
This Week In React #145: Next.js, Server Actions, useFormStatus, useOptimistic, App Router, Canaries, Ink, ReasonML, Redwood, Reanimated, VisionCamera...
📦 Zact - Zod Server ACTions
-
next-safe-action: a library for defining typesafe Next.js Server Actions using TypeScript + Zod
Is this similar to Zact from Theo Browne? https://github.com/pingdotgg/zact
telefunc
-
tRPC – Move Fast and Break Nothing. End-to-end typesafe APIs made easy
Compared with tRPC: https://github.com/brillout/telefunc/issues/9
-
GraphQL vs. REST APIs: a complete guide
For JavaScript based projects TeleFunc[1] can make development way simpler by 'removing' the need for an API.
[1]: https://telefunc.com/
-
Next, Nest, Nuxt Nust?
- 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.
-
Is there a library or a standard way of creating an interface for my api endpoints?
Another suggestion to solve your problem could be to use telefunc
-
Remote Functions. Instead of API
> 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?
-
End-to-end type safety with tRPC (example repository)
An alternativeto tRPC that I find easier to use is telefunc
What are some alternatives?
next-safe-action - Type safe and validated Server Actions in your Next.js (App Router) project.
electron-trpc - Build type-safe Electron inter-process communication using tRPC
sdk-node - Node.js SDK for the Squidex API
vike - 🔨 Flexible, lean, community-driven, dependable, fast Vite-based frontend framework.
surveys - YAML config files for the Devographics surveys
tRPC-example - e2e type safety with tRPC
wundergraph - WunderGraph is a Backend for Frontend Framework to optimize frontend, fullstack and backend developer workflows through API Composition.
stytch-t3-example - An example app demonstrating how to use Stytch within the T3 stack
ts-websocket-compressor - This library compresses data sent over a WebSocket connection to improve throughput on devices that can't use compression for one reason or another.
phero - Full-stack type-safety with pure TypeScript