subscriptions-transport-ws
amplify-js
Our great sponsors
subscriptions-transport-ws | amplify-js | |
---|---|---|
11 | 42 | |
1,515 | 9,363 | |
- | 0.1% | |
6.2 | 9.9 | |
about 2 years ago | 7 days ago | |
TypeScript | TypeScript | |
MIT License | 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.
subscriptions-transport-ws
-
Fixing a 3 second lockup in our app by switching from Apollo Client to URQL
Additionally, we created a bit more work for ourselves by upgrading the library we use for GraphQL subscriptions over web sockets, moving from the seemingly unmaintained subscriptions-transport-ws to the active graphql-ws project (which is URLQ’s library of choice for subscriptions).
- Is this a graphql thing or JSON thing?
-
GraphQL Subscriptions and Mikro-Orm in 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.
-
Looking for GraphQL server with ws-transport ability
I'm looking for graphql server that can do queries and mutations over websocket, like subscriptions-transport-ws. Juniper and async-graphql both looks promising and async-graphql at least uses wording Subscriptions (WebSocket transport) in features but i couldn't find much more or any examples about that from the docs or repo.
-
three ways to deploy a serverless graphQL API
graphql-yoga is built on other packages that provide functionality required for building a GraphQL server such as web server frameworks like express and apollo-server, GraphQL subscriptions with graphql-subscriptions and subscriptions-transport-ws, GraphQL engine & schema helpers including graphql.js and graphql-tools, and an interactive GraphQL IDE with graphql-playground.
-
How does a client know if the server managing its subscription goes offline? (Multiple instances)
The javascript implementation is at subscriptions-transport-ws
-
GraphQL over WebSockets
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.
-
The Stack #3
While subscription-transport-ws from Apollo initially started off this journey, it is not actively maintained and GraphQL WS by Denis definitely is a great replacement to that having no external dependencies and having the ability to work across many frameworks.
-
I need a little help implementing user online status tracking with Apollo/GraphQL.
apollo-server plans to remove WebSocket support, which is currenlty done over the deprecated graphql-ws protocol (as implemented by the unmaintained subscription-transport-ws module by apollo), in the next major version.
-
GraphQL Query and Mutation over Websockets
https://github.com/apollographql/subscriptions-transport-ws, which is used by Apollo Server does support executing queries and mutations actually but you are better off moving away it anyway (check the text in their README!)
amplify-js
-
In Defense of Cognito
One note of caution, though: Amplify uses a frontend-only Cognito integration that stores long-lived, never-rotating refresh tokens in browser storage, where any XSS vulnerability would have access to them. A more secure approach is to implement a couple of backend API routes to store the refresh tokens in `HttpOnly` cookies instead, which I outlined here (option 1 in your case to support SSO). I'll probably open source a solution to do this early next year so we don't all have to keep reinventing this wheel (probably why AWS calls their conference re:invent).
-
Auth0 increases price by 300%
I'm ramosbugs on GitHub (that comment is mine). If you subscribe to https://github.com/aws-amplify/amplify-js/issues/1218 I'll post a comment there once I release a solution.
-
Server-Side Rendering with AWS Amplify
Amplify also lets you host a backend, which it runs in Lambda functions. You don't have a lot of control over it, but it works well for its intended audience: People who wouldn't know what to do if they had a lot of control over their Lambda functions. Amplify also lets you consume other AWS services easily, through declarative and easy-to-use libraries. That way, you can consume Cognito or S3 from the frontend without knowing a lot about Cognito or S3. Here's the complete list of libraries for Amplify, and you can check the Readme of the JavaScript one as an example of its features.
-
React Native Storage.put() results in error
Whenever I call Storage.put() inside my React Native (with Expo) application, I get an error of [TypeError: undefined is not a function]. Doing some internet digging, after hours of searching, I found only one other reference to this kind of error, and that is with the DataStore: https://github.com/aws-amplify/amplify-js/issues/10764
- How was you experience with nextJS using SSR in amplify?
-
SRP_A error when trying Custom Auth Passwordless flow
Hello! Can you please create a GitHub issue here for us to investigate this further? https://github.com/aws-amplify/amplify-js/issues
-
Cookies vs local storage - what to use when?
Thanks for bringing this up. This discussion on the project's github is equally insightful on the subject.
-
Understanding ID Token vs. Access Token in AWS Amplify
Amplify GitHub Issue
-
The Amplify Series, Part 6: Using the power of AI and Machine Learning with Amplify Predictions
Bug: There is currently, at the time of writing, a bug in Amplify that does not allow us to use the voiceId “Kevin”, which we selected when creating the backend resources. Selecting the voiceId “Amy” works, so we will use that.
- RFC: Amplify JS TypeScript Improvements
What are some alternatives?
graphql-ws - Coherent, zero-dependency, lazy, simple, GraphQL over WebSocket Protocol compliant server and client.
microsoft-authentication-library-for-js - Microsoft Authentication Library (MSAL) for JS
uWebSockets.js - μWebSockets for Node.js back-ends :metal:
passwordless-auth - Allows a user to login directly via email without a need for entering passwords using Cognito
mercurius - Implement GraphQL servers and gateways with Fastify
Rollup - Next-generation ES module bundler
ws - Simple to use, blazing fast and thoroughly tested WebSocket client and server for Node.js
apollo-server - 🌍 Spec-compliant and production ready JavaScript GraphQL server that lets you develop in a schema-first way. Built for Express, Connect, Hapi, Koa, and more.
fastify-websocket - basic websocket support for fastify
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.
altair - ✨⚡️ A beautiful feature-rich GraphQL Client for all platforms.
AWS - AWS SDK for iOS. For more information, see our web site: