|11 days ago||3 days ago|
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.
GraphQL Subscriptions: Why we use SSE/Fetch over Websockets
2 projects | reddit.com/r/graphql | 27 Apr 2022
how it subscription work on the apollo server?
3 projects | reddit.com/r/graphql | 26 Apr 2022
Actually WebSocket is not the only protocol for executing GraphQL subscriptions. There is also a graphql-over-sse protocol, which is much more lightweight, and uses Server Sent Events. A popular implementation of it is the graphql-sse library, which is maintained by the same person as graphql-ws. The setup and API of both libraries is pretty similar.
Advice on using graphql-ws with Apollo/React
2 projects | reddit.com/r/graphql | 25 Oct 2021
That said, I feel so close to success that I can't quite give up. I am using graphql-ws as I understand this to be the new standard implementation of GraphQL Subscriptions. However, of course, Apollo subscriptions have not been updated to implement this. So, looking at the Recipes over on the graphql-ws documentation I have found the guide for using Apollo client. However as I am new to Apollo, it is using a lot of terms I am unfamiliar with.
GraphQL Subscriptions and Mikro-Orm in 2021
2 projects | dev.to | 14 Oct 2021
Okay but seriously, if you've fallen down the rabbit hole of Apollo docs pointing you towards one library (subscription-transport-ws) which then points you to another (graphql-ws) , and so on and so forth, then hopefully this helps pull you out.
How does a client know if the server managing its subscription goes offline? (Multiple instances)
2 projects | reddit.com/r/graphql | 23 Sep 2021
The most common protocol used today for subscriptions is the Apollo websocket protocol.
Graphql Subscriptions w/o apollo
1 project | reddit.com/r/graphql | 15 Sep 2021
GraphQL subscriptions are just web sockets. You can check graphql-ws package if you want something without Apollo dependency. Though I don't understand why you want to not depend on it in the first place.
GraphQL Tools V8 - Stitch Federation Services
4 projects | dev.to | 29 Jul 2021
New GraphQL-WS ✔️
Subscriptions and Live Queries - Real Time with GraphQL
5 projects | dev.to | 29 Jul 2021
The interesting thing is that we can use any transport for delivering the results to client. The most popular implementation (as mentioned before) is subscriptions-transport-ws. Unfortunately, since it is poorly maintained, the GraphQL Working Group came up with a new implementation over WebSockets, graphql-ws.
GraphQL over WebSockets
9 projects | dev.to | 29 Jul 2021
Okay, so, how do I use WebSockets to add support for the GraphQL subscription operation? Doing a basic Google search, you’d be faced with a single solution, namely subscriptions-transport-ws. Looking through the repository, checking recent comments, reading through the issues and open PRs - might have you notice the abundance of bugs and their security implications. A summary can be found here.
I need a little help implementing user online status tracking with Apollo/GraphQL.
7 projects | reddit.com/r/graphql | 10 Jun 2021
Have you thought about using graphql-ws instead? It uses the new graphql-transport-ws protocol which also has an open RFC that is discussed in the GraphQL working Groups.
GraphQL error handling to the max with Typescript, codegen and fp-ts
11 projects | dev.to | 7 Mar 2022
:::note GraphQL Union is available for Types only, not for Inputs. However, the oneOf directive will bridge the gap in the future.
Why We Combined GraphQL and a Serverless Distributed Ledger
2 projects | dev.to | 19 Jan 2022
GraphQL is a query language for APIs and a runtime for fulfilling those queries with existing data. GraphQL is a open specification; it is not controlled or managed by a single vendor. GraphQL clients and servers can be written in a number of programming languages. There is no requirement to use particular data stores to persist data.
Consuming GraphQL APIs for REST-minded Developers
1 project | dev.to | 14 Jan 2022
And with that, while there are definitely more advanced things one can learn about GraphQL, you should be armed with enough knowledge about the GraphQL spec to understand how to use and consume most GraphQL APIs.
GraphQL tutorial: How to get started
3 projects | dev.to | 12 Jan 2022
Join multiple GraphQL APIs without Schema Stitching or Federation
3 projects | reddit.com/r/graphql | 6 Jan 2022
Here's an idea: you can use the flat chain syntax. Then you can write the query like this:
Asking for feedback on "joining" disjoint GraphQL APIs
1 project | reddit.com/r/graphql | 3 Jan 2022
What about using @export, as proposed here: https://github.com/graphql/graphql-spec/issues/583?
Aliasing a nested field as a parent field
3 projects | reddit.com/r/graphql | 31 Dec 2021
So check if your server supports the @export functionality, which was also proposed for the spec but not yet approved (unfortunately! this should really be in GraphQL, imo).3 projects | reddit.com/r/graphql | 31 Dec 2021
What you're requesting is a feature that was proposed for the GraphQL spec: the flat chain syntax. With it, you could possibly do this:
The Best Collected Details on the GraphQL Specification – Overview & Language
5 projects | dev.to | 29 Dec 2021
1 project | dev.to | 22 Dec 2021
GraphQL is a specification that describes: a query language and schema definition language. It's not a programming language capable of arbitrary computation, but is instead a language used to make requests to application services that have capabilities defined in this specification. GraphQL does not mandate a particular programming language or storage system for application services that implement it. Instead, application services take their capabilities and map them to a uniform language, type system, and philosophy that GraphQL encodes. This provides a unified interface friendly to product development and a powerful platform for tool-building.
What are some alternatives?
subscriptions-transport-ws - :arrows_clockwise: A WebSocket client + server for GraphQL subscriptions
GraphQL Kotlin - Libraries for running GraphQL in Kotlin
graphql-helix - A highly evolved GraphQL HTTP Server 🧬
ws - Simple to use, blazing fast and thoroughly tested WebSocket client and server for Node.js
graphql-sse - Zero-dependency, HTTP/1 safe, simple, GraphQL over Server-Sent Events Protocol server and client.
better-sqlite3 - The fastest and simplest library for SQLite3 in Node.js.
fastify-websocket - basic websocket support for fastify
graphql-tools - :wrench: Build, mock, and stitch a GraphQL schema using the schema language
Hasura - Blazing fast, instant realtime GraphQL APIs on your DB with fine grained access control, also trigger webhooks on database events.