ts-proto
protobuf-es
Our great sponsors
ts-proto | protobuf-es | |
---|---|---|
8 | 7 | |
1,925 | 932 | |
- | 5.2% | |
9.0 | 9.2 | |
8 days ago | 3 days ago | |
TypeScript | TypeScript | |
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.
protobuf-es
-
gut: convert golang structs to typescript interfaces
Yes, you can. You are mistaking protobuf with gRPC. See this for more information.
-
TypeScript type safety with GO
You can use this with connect: https://github.com/bufbuild/protobuf-es
-
Ask HN: Why isn't JSON-RPC more widely adopted?
Ah you should check out https://github.com/bufbuild/protobuf-es which feels great so far. Then there's connect by the same buf people but it has a grpc-web option https://connect.build/docs/web/getting-started/. The amount of code generated is also tiny, which I love.
-
Connect-Web: ergonomic Protobuf & gRPC for browsers
I'd recommend looking into protobuf-ts (Timo from Buf) or protobuf-es (Buf maintained).
-
Connect-Web: It's time for Protobuf/gRPC to be your first choice in the browser
Not sure if it is a magic bullet, but it was definitely written by TypeScript developers, for TypeScript developers.
The generated TypeScript code is already pretty minimal because all serialization ops are implemented with reflection instead of generated code (which is only marginally slower than generated code in JS).
But you can also switch to generating JavaScript + TypeScript declaration files, which is truly minimal: JavaScript is an entire dynamic language, so we actually only generated a small snippet of metadata in the .js output, and create a class at run time with a function call. The generated typings (.d.ts) give you type safety, autocompletion in the IDE, and so on.
You can see the output here: https://github.com/bufbuild/protobuf-es/blob/main/packages/p...
- Connect: A Better gRPC
What are some alternatives?
protobuf-ts - Protobuf and RPC for TypeScript
connect-go - Moved to https://github.com/connectrpc/connect-go
protoc-gen-typescript-http - Generate types and service clients from protobuf definitions annotated with http rules.
bloomrpc - Former GUI client for gRPC services. No longer maintained.
grpc-web - gRPC for Web Clients
deno-pbf - Deno pbf port of https://github.com/mapbox/pbf
grpcurl - Like cURL, but for gRPC: Command-line tool for interacting with gRPC servers
grpc-web - gRPC Web implementation for Golang and TypeScript
connect-es - The TypeScript implementation of Connect: Protobuf RPC that works.
rpc_ts - Remote Procedure Calls in TypeScript made simple 🤞
fetch - Fetch Standard