What is graphql-tools?
The graphql-tools package is a set of utilities that help in the development of GraphQL schemas and resolvers in JavaScript. It provides tools for schema stitching, schema delegation, and schema transformation, among other functionalities.
What are graphql-tools's main functionalities?
Schema Stitching
Schema stitching allows you to combine multiple GraphQL schemas into a single schema. This is useful for modularizing your GraphQL API and for integrating multiple services.
const { makeExecutableSchema, mergeSchemas } = require('graphql-tools');
const schemaA = makeExecutableSchema({ typeDefs: `type Query { hello: String }`, resolvers: { Query: { hello: () => 'Hello from schema A' } } });
const schemaB = makeExecutableSchema({ typeDefs: `type Query { world: String }`, resolvers: { Query: { world: () => 'World from schema B' } } });
const mergedSchema = mergeSchemas({ schemas: [schemaA, schemaB] });
Schema Delegation
Schema delegation allows you to forward a query from one schema to another. This is useful for creating a unified API that delegates parts of the query to different underlying services.
const { delegateToSchema } = require('graphql-tools');
const schemaA = makeExecutableSchema({ typeDefs: `type Query { hello: String }`, resolvers: { Query: { hello: () => 'Hello from schema A' } } });
const resolvers = {
Query: {
helloFromA: (parent, args, context, info) => delegateToSchema({ schema: schemaA, operation: 'query', fieldName: 'hello', context, info })
}
};
Schema Transformation
Schema transformation allows you to modify an existing schema. This can include renaming types, adding or removing fields, and other modifications. This is useful for adapting third-party schemas to fit your needs.
const { transformSchema, RenameTypes } = require('graphql-tools');
const schema = makeExecutableSchema({ typeDefs: `type Query { hello: String }`, resolvers: { Query: { hello: () => 'Hello' } } });
const transformedSchema = transformSchema(schema, [new RenameTypes(name => `New_${name}`)]);
Other packages similar to graphql-tools
apollo-server
Apollo Server is a community-maintained open-source GraphQL server that works with any GraphQL schema built with graphql-tools. It provides an easy way to set up a GraphQL server with features like schema stitching, schema delegation, and more. Compared to graphql-tools, Apollo Server is more focused on providing a complete server setup, including integrations with various data sources and middleware.
graphql-compose
graphql-compose is a toolkit for generating complex GraphQL schemas in an easier and more readable way. It provides a set of utilities for schema creation, schema stitching, and schema transformation. Compared to graphql-tools, graphql-compose offers a more composable and functional approach to building GraphQL schemas.
GraphQL-tools: generate and mock GraphQL.js schemas
This package provides a few useful ways to create a GraphQL schema:
- Use the GraphQL schema language to generate a schema with full support for resolvers, interfaces, unions, and custom scalars. The schema produced is completely compatible with GraphQL.js.
- Mock your GraphQL API with fine-grained per-type mocking
- Automatically stitch multiple schemas together into one larger API
Documentation
Read the docs.
Binding to HTTP
If you want to bind your JavaScript GraphQL schema to an HTTP server, we recommend using Apollo Server, which supports every popular Node HTTP server library including Express, Koa, Hapi, and more.
JavaScript GraphQL servers are often developed with graphql-tools
and apollo-server-express
together: One to write the schema and resolver code, and the other to connect it to a web server.
Example
See and edit the live example on Launchpad.
When using graphql-tools
, you describe the schema as a GraphQL type language string:
const typeDefs = `
type Author {
id: ID! # the ! means that every author object _must_ have an id
firstName: String
lastName: String
"""
the list of Posts by this author
"""
posts: [Post]
}
type Post {
id: ID!
title: String
author: Author
votes: Int
}
# the schema allows the following query:
type Query {
posts: [Post]
}
# this schema allows the following mutation:
type Mutation {
upvotePost (
postId: ID!
): Post
}
# we need to tell the server which types represent the root query
# and root mutation types. We call them RootQuery and RootMutation by convention.
schema {
query: Query
mutation: Mutation
}
`;
export default typeDefs;
Then you define resolvers as a nested object that maps type and field names to resolver functions:
const resolvers = {
Query: {
posts() {
return posts;
},
},
Mutation: {
upvotePost(_, { postId }) {
const post = find(posts, { id: postId });
if (!post) {
throw new Error(`Couldn't find post with id ${postId}`);
}
post.votes += 1;
return post;
},
},
Author: {
posts(author) {
return filter(posts, { authorId: author.id });
},
},
Post: {
author(post) {
return find(authors, { id: post.authorId });
},
},
};
export default resolvers;
At the end, the schema and resolvers are combined using makeExecutableSchema
:
import { makeExecutableSchema } from 'graphql-tools';
const executableSchema = makeExecutableSchema({
typeDefs,
resolvers,
});
This example has the entire type definition in one string and all resolvers in one file, but you can combine types and resolvers from multiple files and objects, as documented in the modularizing the schema section of the docs.
Contributions
Contributions, issues and feature requests are very welcome. If you are using this package and fixed a bug for yourself, please consider submitting a PR!