protobuf-ts
openapi-generator-cli
protobuf-ts | openapi-generator-cli | |
---|---|---|
13 | 8 | |
951 | 1,290 | |
- | 2.6% | |
6.5 | 8.1 | |
17 days ago | 6 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.
protobuf-ts
-
tRPC – Move Fast and Break Nothing. End-to-end typesafe APIs made easy
DX for front or back end? The beauty of tRPC is that the types are derived/inferred from the backend runtime code (like, as you type). It would be nigh impossible to do that with grpc(-web) using proto files as the source of truth.
It's possible there's a project out there which could automatically produce proto files from something like zod, json-schema, etc. which could be directly interpreted by TS to provide similar (as you type) DX while still allowing some other language backend to consume the derived proto files (though the DX there would be less than ideal).
If you're just looking for similar TS clients/interfaces for grpc-web then I'd recommend https://github.com/timostamm/protobuf-ts which operates on plain JS objects (no new MyMessage().serialize(), instead the code generator mostly produces TS interfaces for you to work against: const myMessage: MyMessage = pojoConformingToInterface; const binary = MyMessage.toBinary(myMessage);)
-
Error using JWT Authentication using GRPC Web in .net 7; postman works - typescript client does not authorize
https://github.com/timostamm/protobuf-ts (RpcMetaData) https://github.com/timostamm/protobuf-ts/blob/main/MANUAL.md
-
gRPC vs REST: Comparing API Styles in Practice
The second big difference is that we now have auto-generated client and server stubs. For this task, I chose to use buf and the protobuf-ts plugin in order to generate idiomatic Typescript classes and objects. Not only do these classes describe the types we'll use in the server and client, but also includes the actual gRPC implementations used to serialize and send messages back and forth across the wire.
-
Why are gRPC and Node.js so difficult?
I wouldn’t use grpc with web if you can avoid it. If you’re looking for a ts protobuf library I can recommend this one https://github.com/timostamm/protobuf-ts
- GRPC Gateway API Client?
-
Building a real-time bidding system with Socket.io and React Native
https://github.com/timostamm/protobuf-ts looks interesting too.
-
Connect-Web: ergonomic Protobuf & gRPC for browsers
I'd recommend looking into protobuf-ts (Timo from Buf) or protobuf-es (Buf maintained).
-
Rust GRPC
Use a GRPC library for frontend, assuming you want to go with Typescript take a look at https://github.com/timostamm/protobuf-ts Frontend frameworks like Angular/React/Vue don't define what and how to implement backend communication. You can use what you want and how you want it.
-
Connect: A Better gRPC
And there's also this which is by the same author but came before it: https://github.com/timostamm/protobuf-ts
The latter has code-generation for services and has various transport packages for twirp, grpc, and grpc-web.
-
Show HN: Pbkit – Protobuf toolkit written in Deno/TypeScript
This looks very interesting! Anything that can move people away from protobuf.js (which seems to no longer be maintained and depends on prototype values for "default values" meaning that you can't send deserialized protobuf messages to/from web workers) and the "native" JS codegen by Google (which produces code that is both very slow and a awkward to use) is a win in my book.
We're currently using https://github.com/timostamm/protobuf-ts which has been fantastic. It's codegen is dependent on the protoc binary as it is implemented as a protoc plugin, but the code it generates passes the protobuf conformance tests. The generated code also outputs plain objects when deserializing protobuf messages which means it works perfectly when sending stuff to/from web workers. It also has grpc, grpc-web, and twirp clients.
openapi-generator-cli
-
Generate DTO models from OpenAPI bundle yml
Hi, I want to create my dto's from a bundle file. This works nearly good, I just don't need all the functions which I am getting. I only need the model structs. I am currently using https://github.com/OpenAPITools/openapi-generator-cli via docker and I am passing the bundle.yml inside. I have the following parameter to only get model files:
-
OpenAPI - API documentation standard - Boon for the software engineers
You can generate boilerplate code stubs with OpenAPI spec. Yes! you heard it right! you only need to write the business logic that’s all, everything will be generated for you. There are so many generators available for every programming language. Find it here https://openapi-generator.tech. GitHub repo for the same https://github.com/OpenAPITools/openapi-generator & https://github.com/OpenAPITools/openapi-generator-cli
-
GRPC Gateway API Client?
- https://github.com/OpenAPITools/openapi-generator-cli
-
Better Fastly API clients with OpenAPI Generator
OAG is a Java project that uses Mustache templates to configure each supported programming language. It provides a CLI openapi-generator-cli that will download the appropriate JAR file and invoke the java executable to run OAG.
-
Publishing Rust types to a TypeScript frontend
So I'm assuming you're talking about generating Rust types from TypeScript? If you can get your typescript definitions into OpenAPI (i.e, via typeconv) you can use the openapi generator cli to generate rust types. However this is geared towards web backends rather than pure IPC or cross-lang interop.
-
I just developed an entire feature without reviewing it in the browser - thanks to Typescript
https://github.com/OpenAPITools/openapi-generator-cli I didn't build it so you may need to do some research on it
-
[AskJS] REST client generation tools
openapi-generator-cli is what I use for openapi/swagger, along with the nestjs swagger plugin. it's not perfect but it gets the job done.
-
Trying out NestJS part 4: Generate typescript clients from OpenAPI documents
The OpenAPI generator configuration file. See Configuration for more info.
What are some alternatives?
ts-proto - An idiomatic protobuf generator for TypeScript
openapi-typescript-code-generator - TypeScript code generator via OpenAPI scheme.
ts-protoc-gen - Protocol Buffers Compiler (protoc) plugin for TypeScript and gRPC-Web.
redoc - 📘 OpenAPI/Swagger-generated API Reference Documentation
grpc-web - gRPC Web implementation for Golang and TypeScript
trying-out-nestjs-part-4
reflect-metadata - Prototype for a Metadata Reflection API for ECMAScript
typoa - 🏗 Build OpenAPI definitions from Typescript typings
deno-pbf - Deno pbf port of https://github.com/mapbox/pbf
openapi-generator - OpenAPI Generator allows generation of API client libraries (SDK generation), server stubs, documentation and configuration automatically given an OpenAPI Spec (v2, v3)
twirp - A simple RPC framework with protobuf service definitions
connect-go - Moved to https://github.com/connectrpc/connect-go