grpc-web
graphql-code-generator
Our great sponsors
grpc-web | graphql-code-generator | |
---|---|---|
33 | 69 | |
8,301 | 10,613 | |
1.2% | - | |
6.5 | 9.1 | |
10 days ago | 5 days ago | |
JavaScript | TypeScript | |
Apache License 2.0 | 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.
grpc-web
-
Ask HN: WebSocket server transforming channel subscriptions to gRPC streams
* Additionally, client can stream data to the backend server (if bidirectional GRPC streams are used). I.e. client sends WebSocket messages, those will be transformed to GRPC messages by WebSocket server and delivered to the application backend.
As a result we have a system which allows to quickly create individual streams by using strict GRPC contract but terminating connections over WebSocket transport. So it works well in web browsers. After that no need to write WebSocket protocol, client implementation, handle WebSocket connection. This all will be solved by a suggested WebSocket server and its client SDKs.
The mechanics is similar to Websocketd (https://github.com/joewalnes/websocketd), but instead of creating OS processes we create GRPC streams. The difference from grpc-web (https://github.com/grpc/grpc-web) is that we provide streaming capabilities but not exposing GRPC contract to the client - just allowing to stream any data as payload (both binary and text) with some wrappers from our client SDKs side for managing subscriptions. I.e. it's not native GRPC streams on the client side - we expose just Connection/Subscription object to stream in both directions. GRPC streams used only for communication between WebSocket server and backend. To mention - grpc-web does not support all kinds of streaming now (https://github.com/grpc/grpc-web#streaming-support) while proposed solution can. This all should provide a cross-platform way to quickly write streaming apps due to client SDKs and language-agnostic nature of GRPC.
I personally see both pros and cons in this scheme (without concentrating on both too much here to keep the question short). I spent some time thinking about this myself, already have some working prototypes – but turned out need more opinions before moving forward with the idea and releasing this, kinda lost in doubts.
My main question - whether this seems interesting for someone here? Do you find this useful and see practical value?
-
Build and Deploy a gRPC-Web App Using Rust Tonic and React
By default, web browsers do not support gRPC, but we will use gRPC-web to make it possible.
-
Lemmy v0.18.0 Release - A reddit alternative written in Rust.
You just have to use a library implementation for JavaScript https://github.com/grpc/grpc-web
-
Full Stack Forays with Go and gRPC
TypeScript support remains an experimental feature of gRPC.
- Seeking Opinion: Choosing Between Gateway and Envoy Proxy for Our Microservices Architecture
-
Introducing Tempo: low latency, cross-platform, end-to-end typesafe APIs
The gRPC-Web protocol supports HTTP/1 and can be used from a browser.
-
gRPC on the client side
-- grpc-web
-
Introduction to gRPC
gRPC is mainly used in server-to-server communication, but it can also be used in client-to-server communication. gRPC-web is a gRPC implementation for web browsers. It is a JavaScript library that allows you to call gRPC services from a web browser. It supports Unary and Streaming Server API calls.
-
gRPC vs REST: Comparing API Styles in Practice
Since we're using Envoy, there's one more neat trick that we can employ. It turns out that Envoy also support gRPC-Web out of the box, a JavaScript client designed to support gRPC communication from the browser! That means that we can send gRPC messages over HTTP/1.1 as base64 encoded strings or as binary protobufs. Messages will be sent through our proxy and on to our backend service. The advantage of this is smaller and more efficient wire communication which should lead to better performance.
-
Understanding gRPC Concepts, Use Cases & Best Practices
protoc-gen-grpc-web — a plugin that allows our front end to communicate with the backend using gRPC calls. A separate blog post on this coming up in the future.
graphql-code-generator
-
Integrating GraphQL Codegen with Storyblok: Step-by-Step Guide
The @graphql-codegen library is a bridge between your GraphQL schema and the actual code you write. It automates the generation of boilerplate code, ensuring that your data fetching layer is always up to date with your content structure.
-
The complete GraphQL Scalar Guide
In typescript and typescript-resolvers plugin v4.0.1, we have reverted the default ID Scalar input type to string. Read the pull request for more details.
-
Looking4Library: A GraphQL client that has query methods on the generated types
See https://github.com/dotansimha/graphql-code-generator with @graphql-codegen/typescript-graphql-request plugin
-
graphql-code-generator VS gqless - a user suggested alternative
2 projects | 2 Jun 2023
-
Making GraphQL Codegen Work For You: GraphQL Integration with React and TypeScript
Graphql Codegen is a code generation library for GraphQL that enables developers to generate custom code. It provides us developers with the ability to generate type definitions, query builders, documentation, and more by analyzing our GraphQL schemas. This makes it easier and faster to build GraphQL applications and reduces the time spent coding.
-
help wanted: Typescript GraphQL Types Response
It is already incoming, with an example in the repository. 😇 https://github.com/dotansimha/graphql-code-generator/pull/8863
-
Why does this package.json script for graphql-codegen only work if the package is installed directly in the package.sjon, even if it already exists in node_modules?
The actual package is @ graphql-codegen/cli
-
Why we ditched GraphQL for tRPC
GraphQL Codegen generates frontend types and React hooks from our GraphQL request definitions.
-
A journey towards a type-safe GraphQL API server
There are two main approaches to keeping the types of the GraphQL schema and entities in business logic in sync. You can generate the schema based on your TypeScript code (e.g. TypeGraphQL), or you can generate types based on your schema (e.g. GraphQL Code Generator). We opted for the latter since it slotted right into our existing GraphQL server implementation using Apollo Server.
-
Move to Hasura/GraphQL for db
For querying in React make sure you use GraphQL code generator https://www.the-guild.dev/graphql/codegen
What are some alternatives?
ngx-grpc - Angular gRPC framework
nexus - Code-First, Type-Safe, GraphQL Schema Construction
grpc-over-webrtc - gRPC over WebRTC
contentful-typescript-codegen - Generate TypeScript interfaces from a Contentful environment
grpcurl - Like cURL, but for gRPC: Command-line tool for interacting with gRPC servers
TypeGraphQL - Create GraphQL schema and resolvers with TypeScript, using classes and decorators!
buf - The best way of working with Protocol Buffers.
TypeORM - ORM for TypeScript and JavaScript. Supports MySQL, PostgreSQL, MariaDB, SQLite, MS SQL Server, Oracle, SAP Hana, WebSQL databases. Works in NodeJS, Browser, Ionic, Cordova and Electron platforms.
webrpc - webrpc is a schema-driven approach to writing backend services for modern Web apps and networks
rtk-query-codegen
evans - Evans: more expressive universal gRPC client
lint-staged - 🚫💩 — Run linters on git staged files