envelop
fetch
envelop | fetch | |
---|---|---|
7 | 35 | |
762 | 2,078 | |
- | 0.5% | |
9.4 | 5.9 | |
3 days ago | 7 days ago | |
TypeScript | HTML | |
MIT License | GNU General Public License v3.0 or later |
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.
envelop
-
Announcing GraphQL Yoga 2.0!
The Guild took over the development of GraphQL Yoga from Prisma in early 2021, and with the growing community of tools in the GraphQL space, most recently Envelop, we were able to rewrite GraphQL Yoga 2.0 from scratch with easy setup, performance, and developer experience at the core.
-
GraphQL Authentication with Envelop and Auth0
Ideally, you already have your basic envelop setup with your http framework of choice. This guide we will be based on the graphql-helix fastify example, but the code can be easily transferred to any other example as listed on our Integrations and Examples documentation. In case you are hitting any roadblocks feel free to reach out to us via the chat box on this page! The full code of the end-result is also available in our examples graphql-helix-auth0 fastify example.
-
Introducing Envelop - The GraphQL Plugin System
Make “hard” GraphQL capabilities easy by installing powerful plugins (Caching, Tracing with Prometheus/DataDog/NewRelic/Sentry/OpenTelemetry/ApolloTracing, Loggers, GraphQL-Jit, Persisted Operations, Security with rate-limit/depth-limit/Auth0 and many others from the Plugins Hub)
-
Introducing Envelop: The GraphQL Plugin System
I started reimplementing the logic from GitHub over here https://github.com/dotansimha/envelop/pull/474
-
Prevent clients from accessing certain resolvers on Apollo server with Prisma
We just today published a new plugin for envelop (GraphQL execution flow customization layer) that allow rejecting GraphQL operations before being executed based on the selection set of the operation. It is pretty flexible and you can limit the access dynamically based on the GraphQL context. E.g. this allows loading the permission information from the database, the user record, or any other remote service. https://github.com/dotansimha/envelop/tree/main/packages/plugins/operation-field-permissions
-
What's the best way to input union types?
We are already having a spec compatible implementation available that you can start using with envelop, without havign to wait for official graphql-js support to land: https://github.com/dotansimha/envelop/pull/179
fetch
- JavaScript fetch does not support GET request with body
-
GitHub Engineering: When MTLS Is Done Wrong
mTLS has warts when used cross-origin. Fetch spec says that pre-flight requests mustn't include client certificates[1], so as a consequence servers behind mTLS authenticated proxy won't get a chance to reply to those pre-flight. Yet for non-preflighted requests it's fine to include client certificates..
[1] https://fetch.spec.whatwg.org/#cors-protocol-and-credentials
-
Node.js fetch() vs. Deno fetch(): Implementation details...
I've been testing full duplex streaming from and to the browser using fetch() in a Native Messaging host. (No browser currently support full duplex streaming even though HTTP/2 does, see Fetch body streams are not full duplex #1254).
-
How do I detect requests initiated by the new fetch standard? How should I detect an AJAX request in general?
Most js libraries use XMLHttpRequest and so provide HTTP_X_REQUESTED_WITH: XMLHttpRequest, but neither Chrome's implementation nor Github's polyfill of the new fetch uses a similar header. So how can one detect that the request is AJAX?
-
Server Sent Events
Any resource of significance should be given a URI. https://www.w3.org/DesignIssues/Axioms.html#uri
Or alternatively,
> Cool URLs don't change (implicitly, cool things have URLs, see above). https://www.w3.org/Provider/Style/URI
The advantage would be so high. It'd become a standard way to assert a resource, to make known a fact, that would be viable across systems. Instead of pushing to a chat app an anonymous chat message in a room, the server could assert a /room/42/msg/c0f3 resource, could identify universally what it is it's sending.
We have come glancingly close to getting such a thing so many times. The HyBi mailing list that begat websockets had a number of alternate more resourceful ideas floating around such as a BEEP protocol that allowed patterns beyond request/response of resources. The browser actually implements an internal protocol that uses HTTP2/push to send resourceful messages... Even though http2/push was de-implemented for webserving in general, and even though ability to hear push events was never implemented (oft requested).
The best we have today is to stream json-ls events, which have an @id property identifying them. But developers would have to snoop these events, and store them in a service worker, to make them actually accessible as http resources.
I continue to hold hope eventually we'll get better at using urls to send data, to assert new things happening... But it's been nearly 30 years of me hoping, and with some fleeting exceptions the browser teams have seemed disinterested in making urls cool, in spite of a number of requests. https://github.com/whatwg/fetch/issues/65 was an old request. https://github.com/whatwg/fetch/issues/607 had some steam in making it happen.
-
[Express] - How to have a self-updating display in browser window? Template Engines sufficient? Or use Vue/Angular/React?]
Fetch
-
Adding timeout and multiple abort signals to fetch() (TypeScript/React)
Proposal: fetch with multiple AbortSignals - I got the idea of merging multiple signals from here.
-
My experience being blocked by Google Safe Browsing
Port 10080 is blocked on most browsers[0] per the WhatWG "bad ports" list[1]. That particular port was added to the list due to the Slipstream attack[2] that made the news a few years ago[3].
You don't have to switch to a browser that ignores standard security mitigations. Just pick a different port for your service.
[0] I just tested Chrome, Firefox, and Safari.
[1] https://fetch.spec.whatwg.org/#bad-port
[2] https://samy.pl/slipstream/
[3] https://news.ycombinator.com/item?id=24955891
-
Substack is now powered by Ghost
Note that caching resources across sites isn't really a thing anymore. See https://github.com/whatwg/fetch/issues/904
- Help with HTTP requests
What are some alternatives?
nestjs-graphql - GraphQL (TypeScript) module for Nest framework (node.js) 🍷
cors-anywhere - CORS Anywhere is a NodeJS reverse proxy which adds CORS headers to the proxied request.
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.
undici - An HTTP/1.1 client, written from scratch for Node.js
graphql-helix - A highly evolved GraphQL HTTP Server 🧬
deno - A modern runtime for JavaScript and TypeScript.
graphql-public-schema-filter - Filter your GraphQL graph into a subgraph. Code-first & SDL-first!
http-proxy - A full-featured http proxy for node.js
graphql-jit - GraphQL execution using a JIT compiler
cors-playground
redwood - The App Framework for Startups
university-domains-list - University Domains and Names Data List & API