ts-proto
connect-go
Our great sponsors
ts-proto | connect-go | |
---|---|---|
8 | 26 | |
1,913 | 3 | |
- | - | |
9.0 | 0.0 | |
8 days ago | 8 months ago | |
TypeScript | Go | |
Apache License 2.0 | Apache License 2.0 |
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.
ts-proto
-
Deno-first implementation of protobuf Reader and Writer
I created it so that I could use `protoc` and `ts-proto` to convert the otel proto files into typescript files.
-
Is TypeScript actually worth It?
Re libraries incompatible with certain typescript versions - e.g. protobufjs fix - it’s been my experience that you want to try and only use compilers specific to each library and compile libraries separately. It’s unfortunate but the JS community often tries to run all JS for a project through the same single compiler tool chain, using one global version of the compiler instead of relying on and effectively linking the JS output for each library. Unless you routinely rewrite third-party libraries to match your toolchain’s expectations, you’re going to have a hard time doing that.
For a library that generates code, that’s a special case, as the code it generates must target a particular language version. You have three choices: 1. Upstream a fix as you propose; 2. Side-by-side install both TS 4.6 and TS 4.7 using workspaces or sub-projects and have some of your code compile with 4.6 and then link the results or 3. Find a replacement that is updated to 4.7. For example, https://github.com/stephenh/ts-proto has 4.7 support listed in its readme.
- Protobuf-ES: The Protocol Buffers TypeScript/JavaScript runtime we all deserve
-
[help] Tonic-build: how to generate generic service definition?
With ts-proto, I can pass a --ts_proto_opt=outputServices=generic-definitions as a flag to protoc to generate "generic service definitions". These definitions contain descriptors for each method, which allows to generate server and client stubs at runtime, and also generate strong types for them at compile time.
-
Connect: A Better gRPC
Curious to see their typescript implementation and how it compares with https://github.com/stephenh/ts-proto which works great for grpc-web.
-
Why isn't gRPC used more for browser to api transport over REST / graphql?
I'm planning on modding https://github.com/stephenh/ts-proto to use https://github.com/ianstormtaylor/superstruct on the client.
-
React Native + gRPC 2021
We also use protobufs and typescript, so we use ts-proto for codegen + binding to grpc services.
-
Typescript clients for invoking Protobuf services over HTTP
Fwiw I maintain ts-proto (https://github.com/stephenh/ts-proto/) and it'd be cool to have the functionality you're building supported in ts-proto at somepoint, if you're curious/want to poke around/etc. :-) Right now there is grpc support via the improbable-eng grpcwebproxy, but supporting GCP's transcoding as well would be great.
connect-go
- Code generation for REST inter service communication?
-
Flutter + gRPC for Desktop and Mobile App Development - Good choice?
In my opinion it's a good idea, it's the architecture we use at work, and it works well for us. The main limitation to be aware of is that many PaaS don't support gRPC traffic (because of the proxies used). For example, DigitalOcean App Platform or Heroku if I remember correctly. If the way you want to host your backend is OK with HTTP/2 and gRPC traffic, then it's not a limitation. One way around this limitation is to use the gRPC-Web protocol, or the Connect protocol (https://connect.build/). Unfortunately, Dart's gRPC client does not support the gRPC-Web protocol outside the web platform. So for a mobile application, it's not usable at the moment. (If this PR were accepted, it would solve the issue: https://github.com/grpc/grpc-dart/pull/557.) As for Connect, no client is currently offered by Buf for Dart. Don't hesitate if you want to know more. That said, I'd advise you to use the Connect implementation for Go to implement your backend. Connect will enable your server to speak all three protocols (gRPC, gRPC-Web and Connect), which is very useful in the long term. What's more, the code is cleaner, and you benefit from official support for observability with OpenTelemetry. If you don't know Buf (the creators of Connect),I suggest you visit their website: https://buf.build/. :-) Good luck!
- How do I provide bot RPC and REST endpoints?
-
Building a modern gRPC-powered microservice using Node.js, Typescript, and Connect
As mentioned in the intro, we are going to use Buf and Connect as our tools. We’ll start by installing the dependencies.
- Ask HN: Is it possible to compile TypeScript to Golang?
-
gRPC + Envoy + grpc-web = scalable multiplexed streaming?
Its annoying, because the rest of Connect (https://connect.build/) looks really really cool. But its no good for me in a complex app if I can't have multiple streams from the server :/
-
Issues with proxying gRPC services to web, and a potential prototype
Consider checking out https://connect.build from https://buf.build. Supports a simpler protocol than grpc-web. Includes a js/ts client for frontend. Then you don’t necessarily need a rest layer, but could leverage the proxy your building.
-
Best Web Sever Framework?
Twirp (though I'd move to https://connect.build for my next project) to do JSON based RPC using protobufs.
-
GRPC Gateway API Client?
my backend is go via https://github.com/bufbuild/connect-go , it's stable and all open source. just try and test it for your purpose. my project run all in 300 server more....
- Connect – A Better gRPC
What are some alternatives?
protobuf-ts - Protobuf and RPC for TypeScript
grpc-go - The Go language implementation of gRPC. HTTP/2 based RPC
protoc-gen-typescript-http - Generate types and service clients from protobuf definitions annotated with http rules.
grpc-gateway - gRPC to JSON proxy generator following the gRPC HTTP spec
protobuf-es - Protocol Buffers for ECMAScript. The only JavaScript Protobuf library that is fully-compliant with Protobuf conformance tests.
grpc-web - gRPC for Web Clients
twirp - A simple RPC framework with protobuf service definitions
deno-pbf - Deno pbf port of https://github.com/mapbox/pbf
examples-go - An example Go server built with Connect.
grpc-web - gRPC Web implementation for Golang and TypeScript
drpc - drpc is a lightweight, drop-in replacement for gRPC