Package Exports
- koa-graphql
This package does not declare an exports field, so the exports above have been automatically detected and optimized by JSPM instead. If any package subpath is missing, it is recommended to post an issue to the original package (koa-graphql) to support the "exports" field. If that is not possible, create a JSPM override to customize the exports field for this package.
Readme
GraphQL Koa Middleware
Create a GraphQL HTTP server with Koa.
Port from express-graphql
Install
npm install --save koa-graphqlUsage
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.
Options
The graphqlHTTP function accepts the following options:
schema: AGraphQLSchemainstance fromgraphql-js. Aschemamust be provided.rootValue: A value to pass as the rootValue to thegraphql()function fromgraphql-js.pretty: Iftrue, any JSON response will be pretty-printed.graphiql: Iftrue, may present GraphiQL when loaded directly from a browser (a useful tool for debugging and exploration).
HTTP Usage
Once installed at a path, express-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 providedquerycontains multiple named operations, this specifies which operation should be executed. If not provided, a 400 error will be returned if thequerycontains multiple named operations.raw: If thegraphiqloption is enabled and therawparameter 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 thequeryparameter.
Advanced Options
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 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
}
}
}
});Contributing
Welcome pull requests!
License
BSD-3-Clause