Security News
Oracle Drags Its Feet in the JavaScript Trademark Dispute
Oracle seeks to dismiss fraud claims in the JavaScript trademark dispute, delaying the case and avoiding questions about its right to the name.
koa-graphql
Advanced tools
Create a GraphQL HTTP server with Koa.
Port from express-graphql
npm install --save koa-graphql
var koa = require('koa');
var mount = require('koa-mount');
var graphqlHTTP = require('koa-graphql');
var app = koa();
app.use(mount('/graphql', graphqlHTTP({ schema: MyGraphQLSchema, graphiql: true })));
NOTE: Below is a copy from express-graphql's README. In this time I implemented almost same api, but it may be changed as time goes on.
The graphqlHTTP
function accepts the following options:
schema
: A GraphQLSchema
instance from graphql-js
.
A schema
must be provided.
rootValue
: A value to pass as the rootValue to the graphql()
function from graphql-js
.
pretty
: If true
, any JSON response will be pretty-printed.
formatError
: An optional function which will be used to format any
errors produced by fulfilling a GraphQL operation. If no function is
provided, GraphQL's default spec-compliant formatError
function will
be used.
validationRules
: Optional additional validation rules queries must
satisfy in addition to those defined by the GraphQL spec.
graphiql
: If true
, may present GraphiQL when loaded directly
from a browser (a useful tool for debugging and exploration).
During development, it's useful to get more information from errors, such as
stack traces. Providing a function to formatError
enables this:
formatError: error => ({
message: error.message,
locations: error.locations,
stack: error.stack
})
Once installed at a path, koa-graphql
will accept requests with
the parameters:
query
: A string GraphQL document to be executed.
variables
: The runtime values to use for any GraphQL query variables
as a JSON object.
operationName
: If the provided query
contains multiple named
operations, this specifies which operation should be executed. If not
provided, a 400 error will be returned if the query
contains multiple
named operations.
raw
: If the graphiql
option is enabled and the raw
parameter is
provided raw JSON will always be returned instead of GraphiQL even when
loaded from a browser.
GraphQL will first look for each parameter in the URL's query-string:
/graphql?query=query+getUser($id:ID){user(id:$id){name}}&variables={"id":"4"}
If not found in the query-string, it will look in the POST request body.
If a previous middleware has already parsed the POST body, the request.body
value will be used. Use multer
or a similar middleware to add support
for multipart/form-data
content, which may be useful for GraphQL mutations
involving uploading files. See an example using multer.
If the POST body has not yet been parsed, graphql-express will interpret it depending on the provided Content-Type header.
application/json
: the POST body will be parsed as a JSON
object of parameters.
application/x-www-form-urlencoded
: this POST body will be
parsed as a url-encoded string of key-value pairs.
application/graphql
: The POST body will be parsed as GraphQL
query string, which provides the query
parameter.
In order to support advanced scenarios such as installing a GraphQL server on a dynamic endpoint or accessing the current authentication information, koa-graphql allows options to be provided as a function of each koa request.
This example uses koa-session
to run GraphQL on a rootValue based on
the currently logged-in session.
var koa = require('koa');
var mount = require('koa-mount');
var session = require('koa-session');
var graphqlHTTP = require('koa-graphql');
var app = koa();
app.keys = [ 'some secret hurr' ];
app.use(session(app));
app.use(function *(next) {
this.session.id = 'me';
yield next;
});
app.use(mount('/graphql', graphqlHTTP((request, context) => ({
schema: MySessionAwareGraphQLSchema,
rootValue: { session: context.session },
graphiql: true
}))));
Then in your type definitions, access session
from the rootValue:
new GraphQLObjectType({
name: 'MyType',
fields: {
myField: {
type: GraphQLString,
resolve(parentValue, _, { rootValue: { session } }) {
// use `session` here
}
}
}
});
Please checkout awesome-graphql.
Welcome pull requests!
BSD-3-Clause
FAQs
Production ready GraphQL Koa middleware.
The npm package koa-graphql receives a total of 2,846 weekly downloads. As such, koa-graphql popularity was classified as popular.
We found that koa-graphql demonstrated a not healthy version release cadence and project activity because the last version was released a year ago. It has 2 open source maintainers collaborating on the project.
Did you know?
Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.
Security News
Oracle seeks to dismiss fraud claims in the JavaScript trademark dispute, delaying the case and avoiding questions about its right to the name.
Security News
The Linux Foundation is warning open source developers that compliance with global sanctions is mandatory, highlighting legal risks and restrictions on contributions.
Security News
Maven Central now validates Sigstore signatures, making it easier for developers to verify the provenance of Java packages.