graphql-sse
fetch-event-source
Our great sponsors
graphql-sse | fetch-event-source | |
---|---|---|
4 | 2 | |
365 | 1,229 | |
- | 12.8% | |
8.0 | 0.0 | |
1 day ago | 28 days ago | |
TypeScript | TypeScript | |
MIT License | 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.
graphql-sse
-
Graph-ql subscriptions without Apollo
The GraphQL over SSE in its simplest form IMHO does not require an additional client library. Setting up a subscription in the browser is as simple as doing the following:
-
GraphQL Subscriptions: Why we use SSE/Fetch over Websockets
There is already a JavaScript implementation for server + client with support for multiplexing from the same maintainer of graphql-ws: graphql-sse
-
how it subscription work on the apollo server?
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.
-
GraphQL over SSE (Server-Sent Events)
graphql-sse is a reference implementation of the GraphQL over Server-Sent Events Protocol aiming to become a part of the GraphQL over HTTP standard.
fetch-event-source
-
How I put ChatGPT into a WYSIWYG editor
The EventSource Web API for handling SSEs (built into most modern browsers) unfortunately supports only GET requests, which was quite limiting when a POST request with larger body JSON data was required. As an alternative, you can use the Fetch API or a ready library like Microsoft’s Fetch Event Source.
-
GraphQL over SSE (Server-Sent Events)
Aforementioned limitations are taken care with a specialised SSE client (inspired by the awesome @microsoft/fetch-event-source) and two separate connection modes: the HTTP/1 safe "single connection mode" that uses a single SSE connection for receiving events with separate HTTP requests dictating the behaviour, and the HTTP/2+ "distinct connections mode" that uses distinct SSE connections for each GraphQL operation, accommodating the parameters in the request itself.
What are some alternatives?
better-sse - ⬆ Dead simple, dependency-less, spec-compliant server-side events implementation for Node, written in TypeScript.
graphql-ws - Coherent, zero-dependency, lazy, simple, GraphQL over WebSocket Protocol compliant server and client.
fastify - Fast and low overhead web framework, for Node.js
aws-lambda-graphql - Use AWS Lambda + AWS API Gateway v2 for GraphQL subscriptions over WebSocket and AWS API Gateway v1 for HTTP
Express - Fast, unopinionated, minimalist web framework for node.
graphql-over-http - Working draft of "GraphQL over HTTP" specification
vrite - Open-source developer content platform | Now in Public Beta
WHATWG HTML Standard - HTML Standard
openai-node - The official Node.js / Typescript library for the OpenAI API
graphql-yoga - 🧘 Rewrite of a fully-featured GraphQL Server with focus on easy setup, performance & great developer experience. The core of Yoga implements WHATWG Fetch API and can run/deploy on any JS environment.