Results for js-to-graphql

JavaScript class that render GraphQL. Better TypeScript + GraphQL experience.

A Query Language and Runtime which can target any service.

A JavaScript template literal tag that parses GraphQL queries

OpenTelemetry instrumentation for `graphql` gql query language and runtime for GraphQL

Minimal GraphQL client supporting Node and browsers for scripts or simple apps.

A data loading utility to reduce requests to a backend via batching and caching.

The easiest way to configure your development environment with your GraphQL schema (supported by most tools, editors & IDEs)

A spec-compliant client-side GraphQL implementation

Validation rule for GraphQL query complexity analysis

A collection of scalar types not included in base GraphQL.

GraphQL subscriptions for node.js

Core engine for Apollo GraphQL server

Coherent, zero-dependency, lazy, simple, GraphQL over WebSocket Protocol compliant server and client

GraphQL JIT Compiler to JS

A library to help construct a graphql-js server supporting react-relay.

GitHub GraphQL API client for browsers and Node

JSON scalar types for GraphQL.js

GraphQL plugin for ESLint

Extendable client for GitHub's REST & GraphQL APIs

HTTP transport layer for GraphQL

A set of RFC 3339 compliant date/time GraphQL scalar types.

Octokit plugin to paginate GraphQL API endpoint responses

A set of utils for faster development of GraphQL tools

A websocket transport for GraphQL subscriptions

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.