Programming

17398 readers

145 users here now

Welcome to the main community in programming.dev! Feel free to post anything relating to programming here!

Cross posting is strongly encouraged in the instance. If you feel your post or another person's post makes sense in another community cross post into it.

Hope you enjoy the instance!

Rules

Follow the programming.dev instance rules
Keep content related to programming in some way
If you're posting long videos try to add in some form of tldr for those who don't want to watch videos

Wormhole

Follow the wormhole through a path of communities [email protected]

founded 1 year ago

MODERATORS

[email protected]

Cuple RPC: Typesharing between frontend and backends made easy. The missing type-safety for full-stack. (lemmy.ml)

submitted 5 months ago by [email protected] to c/[email protected]

2 comments fedilink hide all child comments

Hey, I'm not a fan of advertising libraries, but otherwise, nobody will know them. I think this package is really spot on and solves many issues with current web technologies.

I'd like to continue this project. If you found it interesting please give some feedback.

github.com/fxdave/cuple
intro: The Missing Type-Safety for Full-Stack

you are viewing a single comment's thread
view the rest of the comments

[–] [email protected] 4 points 5 months ago* (last edited 5 months ago)

Thanks for the question. GraphQL works with multiple languages, Cuple works only with Typescript. Despite this drawback this also gives you some advantages:

The Request and Response types are auto-inferred from the endpoint you write
Because the types are in Typescript you don't need to generate a client, you just simply use it with @cuple/client and get instant feedback.
You don't have to learn another language. It's just typescript.

Practically it means less boilerplate and it let's you focus on the feature you write. Cuple is also not a query language, you get what the server sends you, it's more likely a type-safe FFI binding. With Cuple you can build a REST API, or anything similar to that with HTTP method, header, path, query, body, and you can use it type-safely.