2016-09-09 20:22:13 -05:00
# GraphQL Server for Express, Connect, Hapi and Koa
2016-04-24 16:00:42 -07:00
2016-04-24 16:03:52 -07:00
[](https://badge.fury.io/js/apollo-server)
[](https://travis-ci.org/apollostack/apollo-server)
[](https://coveralls.io/github/apollostack/apollo-server?branch=master)
2016-07-28 10:14:05 -07:00
[](http://www.apollostack.com/#slack )
2016-04-24 16:00:42 -07:00
2016-09-09 20:22:13 -05:00
Apollo Server is a community-maintained open-source GraphQL server. It works with all Node.js HTTP server frameworks: Express, Connect, Hapi and Koa.
2016-04-24 16:00:42 -07:00
2016-08-01 12:54:47 -07:00
## Principles
2016-04-24 16:00:42 -07:00
2016-08-01 12:54:47 -07:00
Apollo Server is built with the following principles in mind:
2016-06-10 22:22:38 -07:00
2016-08-01 12:54:47 -07:00
* **By the community, for the community**: Apollo Server's development is driven by the needs of developers
* **Simplicity**: by keeping things simple, Apollo Server is easier to use, easier to contribute to, and more secure
* **Performance**: Apollo Server is well-tested and production-ready - no modifications needed
2016-06-10 22:22:38 -07:00
2016-08-01 12:54:47 -07:00
Anyone is welcome to contribute to Apollo Server, just read [CONTRIBUTING.md ](./CONTRIBUTING.md ), take a look at the [roadmap ](./ROADMAP.md ) and make your first PR!
2016-06-10 22:22:38 -07:00
2016-08-01 12:54:47 -07:00
## Getting started
2016-09-13 21:30:32 -07:00
Apollo Server is super-easy to set up. Just npm-install apollo-server, write a GraphQL schema, and then use one of the following snippets to get started. For more info, read the [Apollo Server docs ](http://dev.apollodata.com/tools/apollo-server/index.html ).
2016-08-01 12:54:47 -07:00
2016-09-29 17:46:40 +03:00
### Installation
2016-08-02 10:04:15 -07:00
2016-10-05 02:11:42 +03:00
Just run `npm install --save apollo-server-<variant>` and you're good to go!
where variant is one of the following:
- express
- koa
- hapi
2016-08-02 10:40:40 -07:00
2016-08-01 12:54:47 -07:00
### Express
```js
import express from 'express';
2016-10-05 02:11:42 +03:00
import { apolloExpress } from 'apollo-server-express';
2016-08-01 12:54:47 -07:00
const myGraphQLSchema = // ... define or import your schema here!
const PORT = 3000;
var app = express();
app.use('/graphql', bodyParser.json(), apolloExpress({ schema: myGraphQLSchema }));
app.listen(PORT);
```
### Connect
```js
2016-08-29 12:35:30 +02:00
import connect from 'connect';
2016-10-05 10:57:45 -05:00
import bodyParser from 'body-parser';
2016-10-05 02:11:42 +03:00
import { apolloConnect } from 'apollo-server-express';
2016-10-05 10:57:45 -05:00
import http from 'http';
2016-08-01 12:54:47 -07:00
const PORT = 3000;
var app = connect();
2016-10-05 10:57:45 -05:00
app.use('/graphql', bodyParser.json());
app.use('/graphql', apolloConnect({ schema: myGraphQLSchema }));
2016-08-01 12:54:47 -07:00
2016-10-05 10:57:45 -05:00
http.createServer(app).listen(PORT);
2016-08-01 12:54:47 -07:00
```
2016-09-09 20:22:13 -05:00
### Hapi
2016-09-09 07:49:23 -05:00
2016-09-14 20:35:32 -07:00
Now with the Hapi plugins `apolloHapi` and `graphiqlHapi` you can pass a route object that includes options to be applied to the route. The example below enables CORS on the `/graphql` route.
2016-09-09 07:49:23 -05:00
2016-08-01 12:54:47 -07:00
```js
import hapi from 'hapi';
2016-10-05 02:11:42 +03:00
import { apolloHapi } from 'apollo-server-hapi';
2016-08-01 12:54:47 -07:00
const server = new hapi.Server();
const HOST = 'localhost';
const PORT = 3000;
server.connection({
host: HOST,
port: PORT,
});
server.register({
2016-09-14 20:35:32 -07:00
register: apolloHapi,
options: {
path: '/graphql',
apolloOptions: {
schema: myGraphQLSchema,
},
route: {
cors: true
}
},
2016-08-01 12:54:47 -07:00
});
2016-09-02 01:07:46 -07:00
server.start((err) => {
if (err) {
throw err;
}
console.log(`Server running at: ${server.info.uri}` );
});
2016-08-01 12:54:47 -07:00
```
2016-09-09 07:49:23 -05:00
2016-08-01 12:54:47 -07:00
### Koa
```js
import koa from 'koa';
import koaRouter from 'koa-router';
2016-10-05 02:11:42 +03:00
import { apolloKoa } from 'apollo-server-koa';
2016-08-01 12:54:47 -07:00
const app = new koa();
const router = new koaRouter();
const PORT = 3000;
app.use(koaBody());
router.post('/graphql', apolloKoa({ schema: myGraphQLSchema }));
app.use(router.routes());
app.use(router.allowedMethods());
app.listen(PORT);
```
## Options
2016-08-20 20:33:20 -07:00
Apollo Server can be configured with an options object with the the following fields:
2016-08-01 12:54:47 -07:00
* **schema**: the GraphQLSchema to be used
* **context**: the context value passed to resolvers during GraphQL execution
* **rootValue**: the value passed to the first resolve function
* **formatError**: a function to apply to every error before sending the response to clients
* **validationRules**: additional GraphQL validation rules to be applied to client-specified queries
* **formatParams**: a function applied for each query in a batch to format parameters before execution
* **formatResponse**: a function applied to each response after execution
All options except for `schema` are optional.
2016-08-20 20:33:20 -07:00
### Whitelisting
The `formatParams` function can be used in combination with the `OperationStore` to enable whitelisting.
```js
const store = new OperationStore(Schema);
store.put('query testquery{ testString }');
apolloOptions = {
schema: Schema,
formatParams(params) {
params['query'] = store.get(params.operationName);
return params;
},
};
```
2016-08-01 12:54:47 -07:00
## Differences to express-graphql
Apollo Server and express-graphql are more or less the same thing (GraphQL middleware for Node.js), but there are a few key differences:
2016-09-09 20:22:13 -05:00
* express-graphql works with Express and Connect, Apollo Server supports Express, Connect, Hapi and Koa.
2016-08-01 12:54:47 -07:00
* express-graphql's main goal is to be a minimal reference implementation, whereas Apollo Server's goal is to be a complete production-ready GraphQL server.
* Compared to express-graphql, Apollo Server has a simpler interface and supports exactly one way of passing queries.
* Apollo Server separates serving GraphiQL (GraphQL UI) from responding to GraphQL requests.
* express-graphql contains code for parsing HTTP request bodies, Apollo Server leaves that to standard packages like body-parser.
2016-08-20 20:33:20 -07:00
* Includes an `OperationStore` to easily manage whitelisting
2016-08-02 10:04:15 -07:00
* Built with TypeScript
2016-08-01 12:54:47 -07:00
2016-08-01 13:31:26 -07:00
Despite express-graphql being a reference implementation, Apollo Server is actually easier to understand and more modular than express-graphql.
2016-08-01 12:54:47 -07:00
That said, Apollo Server is heavily inspired by express-graphql (it's the reference implementation after all). Rather than seeing the two as competing alternatives, we think that they both have separate roles in the GraphQL ecosystem: express-graphql is a reference implementation, and Apollo Server is a GraphQL server to be used in production and evolve quickly with the needs of the community. Over time, express-graphql can adopt those features of Apollo Server that have proven their worth and become established more widely.
2016-09-10 18:37:14 -04:00
## Apollo Server Development
If you want to develop apollo server locally you must follow the following instructions:
* Fork this repository
* Install the Apollo Server project in your computer
```
git clone https://github.com/[your-user]/apollo-server
cd apollo-server
2016-10-05 02:11:42 +03:00
npm run bootstrap
cd packages/apollo-server-< variant > /
2016-09-10 18:37:14 -04:00
npm link
```
* Install your local Apollo Server in other App
```
cd ~/myApp
npm link apollo-server
```