Introduction

There are many ways to configure your application to use GraphQL, and while it is often enough to specify configuration options directly in your application code, maintaining and understanding the hard-coded configuration options may become a challenge as the scale grows. We recommend configuring your application with a .graphqlrc file that contains commonly needed GraphQL-related artifacts.

Think about GraphQL Config as one configuration for all your GraphQL tools.

The basic idea is to have one configuration file that any GraphQL tool could consume.

As a Developer

From the developer perspective, you gain simplicity and a central place to setup libraries, tools and your IDE extensions.

As a Library Author

From the point of view of a library author, GraphQL Config makes it easier to maintain the code responsible for handling configuration, loading GraphQL schemas or even files with GraphQL operations and fragments. GraphQL Config provides a set of useful methods and an easy-to-work-with API.

Examples

Learn more in usage docs.

.graphqlrc or .graphqlrc.yml/yaml

schema: 'packages/api/src/schema.graphql'
documents: 'packages/app/src/components/**/*.graphql'
extensions:
  customExtension:
    foo: true

.graphqlrc, graphql.config.json or .graphqlrc.json

{
  "schema": "https://localhost:8000"
}

graphql.config.toml or .graphqlrc.toml

schema = "https://localhost:8080"

graphql.config.js or .graphqlrc.js

module.exports = {
  schema: 'https://localhost:8000'
}

graphql.config.ts or .graphqlrc.ts

import type { IGraphQLConfig } from 'graphql-config'
 
const config: IGraphQLConfig = {
  schema: 'https://localhost:8000'
}
 
export default config

Custom Paths

Custom extension paths with .mycustomrc.js, mycustom.config.yml, etc. - any filename listed in usage docs with graphql replaced by the loadConfig() parameter configName.

await loadConfig({ configName: 'mycustom' })

would allow you to use .mycustomrc.js:

module.exports = {
  schema: 'https://localhost:8000'
}

Lookup Order

We are using cosmiconfig to load the schema, and it uses the following flow to look for configurations:

1. a package.json property.
2. a JSON or YAML, extensionless “rc file”.
3. a “rc file” with the extensions .json, .yaml, .yml, .toml, .ts or .js.
4. a .config.js CommonJS module, or a .config.ts file.