GraphQL Express Middleware

A fork of express-graphql for our convenience.

Create a GraphQL HTTP server with Express.

1npm install --save widgetizer-express

Install widgetizer-express as middleware in your express server:

1var graphqlHTTP = require('widgetizer-express');
2
3var app = express();
4
5app.use('/graphql', graphqlHTTP({ schema: MyGraphQLSchema, graphiql: true }));

Options

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).

Debugging

During development, it's useful to get more information from errors, such as stack traces. Providing a function to formatError enables this:

1formatError: error => ({
2  message: error.message,
3  locations: error.locations,
4  stack: error.stack
5})

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 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.

Advanced Options

In order to support advanced scenarios such as installing a GraphQL server on a dynamic endpoint or accessing the current authentication information, express-graphql allows options to be provided as a function of each express request.

This example uses express-session to run GraphQL on a rootValue based on the currently logged-in session.

1var session = require('express-session');
2var graphqlHTTP = require('express-graphql');
3
4var app = express();
5
6app.use(session({ secret: 'keyboard cat', cookie: { maxAge: 60000 }}));
7
8app.use('/graphql', graphqlHTTP(request => ({
9  schema: MySessionAwareGraphQLSchema,
10  rootValue: { session: request.session },
11  graphiql: true
12})));

Then in your type definitions, access session from the rootValue:

1new GraphQLObjectType({
2  name: 'MyType',
3  fields: {
4    myField: {
5      type: GraphQLString,
6      resolve(parentValue, _, { rootValue: { session } }) {
7        // use `session` here
8      }
9    }
10  }
11});