Genereate graphql queries, mutations and subscriptions based on a schema
Automatically generate GraphQL operations from a schema
Utilities for GraphQL documents.
The Linear Client SDK for interacting with the Linear GraphQL API
An exchange for operation retry support in urql
A tool for converting GraphQL Schema Definition Language (SDL) to Protocol Buffers and mapping files.
The easiest way to configure your development environment with your GraphQL schema (supported by most tools, editors & IDEs)
Creates a Persisted Query Manifest from an Apollo Client Web project
GraphQL codegen plugin that generates only the types used in the operations
A Query Language and Runtime which can target any service.
Jest Plugin to load and parse imported GraphQL files
A flexible in-memory store based on a GraphQL Schema
monday.com API client
Easily generate GraphQL operations for provided schema. Our motivation was to create the plugin to create operations for further processing by GraphQL Codegen (in our case to generate SWR and graphql-request SDK out of the box for basic CRUD operations).
An esbuild plugin that allows for the importing of GraphQL files
Useful tools to create and manipulate GraphQL schemas.
GraphQL types and code generator based on schema
This library provide playwright integration with graphql for efficient API tests.
TypeScript Language Service Plugin for GraphQL
OpenTelemetry instrumentation for `graphql` gql query language and runtime for GraphQL
No description provided.
WebSocket transport layer for GraphQL
Coherent, zero-dependency, lazy, simple, GraphQL over WebSocket Protocol compliant server and client
A JavaScript template literal tag that parses GraphQL queries
Surikat is a web framework that revolves around GraphQL, offering a lot of ready-made functionality such as CRUD operations, automatic query generation, authentication and performance optimisations.
The middleware makes sure any request to specified paths would have been preflighted if it was sent by a browser. We don't want random websites to be able to execute actual GraphQL operations from a user's browser unless our CORS policy supports it. It's not good enough just to ensure that the browser can't read the response from the operation; we also want to prevent CSRF, where the attacker can cause side effects with an operation or can measure the timing of a read operation. Our goal is to ensure that we don't run the context function or execute the GraphQL operation until the browser has evaluated the CORS policy, which means we want all operations to be pre-flighted. We can do that by only processing operations that have at least one header set that appears to be manually set by the JS code rather than by the browser automatically. POST requests generally have a content-type `application/json`, which is sufficient to trigger preflighting. So we take extra care with requests that specify no content-type or that specify one of the three non-preflighted content types. For those operations, we require one of a set of specific headers to be set. By ensuring that every operation either has a custom content-type or sets one of these headers, we know we won't execute operations at the request of origins who our CORS policy will block.