JSON scalar types for GraphQL.js
TypeScript definitions for graphql-type-json
A collection of scalar types not included in base GraphQL.
A Query Language and Runtime which can target any service.
JSON scalar types for GraphQL.js
GraphQL subscriptions for node.js
A spec-compliant client-side GraphQL implementation
Create GraphQL schema and resolvers with TypeScript, using classes and decorators!
full service, official monaco mode for GraphQL
Minimal GraphQL client supporting Node and browsers for scripts or simple apps.
GitHub GraphQL API client for browsers and Node
The spec-compliant & magical GraphQL query language engine in the TypeScript type system
Simple, pluggable, zero-dependency, GraphQL over HTTP spec compliant server, client and audit suite.
GraphQL server middleware to support application/graphql requests
A core runtime for building GraphQL-driven applications.
`graphql-2-json-schema` package
This package generates GraphQL Schema from JSON Schema and sample JSON request and responses. You can define your root field endpoints like below in your GraphQL Config for example;
Generate object types, inputs, args, etc. from prisma schema file for usage with @nestjs/graphql module
A data loading utility to reduce requests to a backend via batching and caching.
Shopify GraphQL Client - A lightweight generic GraphQL JS client to interact with Shopify GraphQL APIs
A library to help construct a graphql-js server supporting react-relay.
Types for building GraphQL language services for IDEs
A tool that generates a strongly typed client library for any GraphQL endpoint. The client allows writing GraphQL queries as plain JS objects (with type safety, awesome code completion experience, custom scalar type mapping, type guards and more)
GraphQL ESLint plugin.
Extra types for graphql-ruby: JSON, Date, and BigInt
GraphQL interface over WCC::Contentful store
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.
No description provided.
No description provided.
No description provided.
No description provided.