So now when your new plugin is ready, you can either maintain it in your own repo and npm package, or you can contribute and make it part of the GraphQL Code Generator repo.

Our repository contains plugins for all languages and platforms, and if your plugin could be helpful for other, please consider to create a PR and maintain it in our repo. This will also promise to run your tests against the latest core changes, and make sure that there are no breaking changes that effect your plugin.

1. Requirements#

To be able to clone, build and develop codegen, you'll need to have the following installed:

GraphQL Code Generator is using the following stack to manage the source code:

  1. TypeScript - for writing the code
  2. Bob - for building, bundling and development workflow
  3. Jest - for running tests.

2. Fork and Clone#

Start by creating a Fork in GitHub, this will allow you to make changes and push them easily later.

Then, use Git to clone your newly created fork repository.

It's also recommended to create a new Git branch at this point, from master branch.

3. Install Dependencies#

GraphQL Code Generator is built as a monorepo, using Yarn Workspaces, so it means that all scripts and dependencies are located in the root package.json of the project.

So now that you have a local copy of the project, start by installing the dependencies for all packages in the repo, by running the following in the root directory of the project:


If you make changes, add libraries or new packages, make sure to install the dependencies again, but always from the root directory, otherwise you'll break the monorepo structure.

4. Make sure everything works#

To test the initial scripts and verify that you have a valid development environment, start by running thw following scripts from the root directory:

yarn build
yarn test

The command above will make sure to build all common/core packages, and will make sure that all tests are passing.

5. Add your plugin#

To add your plugin, start by creating a directory for it. All existing plugins are located under packages/plugins/ directory, so add it there.

Now, create a simple package.json (or, you can copy from other plugins...)

Make sure to follow the following instructions:

  1. Make sure the package name starts with @graphql-codegen/ prefix.
"name": "@graphql-codegen/MY_PLUGIN_NAME",
  1. Make sure that the version is aligned with all other existing packages.
"version": "X.Y.Z",

The current version of the codegen is: Codegen version

  1. Make sure that you have the following scripts configured;
"scripts": {
"lint": "eslint **/*.ts",
"test": "jest --no-watchman --config ../../../../jest.config.js",
"prepack": "bob prepack"

This will make sure that your plugin is compatible with our build and test system.

  1. Make sure your basic plugin dependencies are configured this way:
"dependencies": {
"@graphql-codegen/plugin-helpers": "X.Y.Z",
"tslib": "~1.11.1"
"peerDependencies": {
"graphql": "^0.12.0 || ^0.13.0 || ^14.0.0 || ^15.0.0"

graphql must be a devDependency in order to allow develoeprs to choose their own version.

tslib is required to compile plugins.

@graphql-codegen/plugin-helpers contains helpful types and utils. Make sure it has the same version as your package.

Now that your plugin is configured, you need to make sure Yarn knows about it and links it to the monorepo, so run the following command again, in the root direcory:


6. Create your plugin#

To create your new plugin, simply create src/index.ts in your plugin directory, and start with the following:

import { PluginFunction, Types } from '@graphql-codegen/plugin-helpers';
export type MyPluginConfig = {
name: string;
export const plugin: PluginFunction<Partial<MyPluginConfig>, MyPluginConfig> = (
schema: GraphQLSchema,
documents: Types.DocumentFile[],
config: TypeScriptDocumentsPluginConfig
) => {
return `Hello ${ || 'anonymous'}!`;

schema is the merged GraphQLSchema object, from all sources. this will always be available for plugin.

documents is an array of GraphQL operations (query/mutatation/subscription/fragment). This is optional, and you can use it only if your plugin needs it.

config is the merged configuration passed in the .yaml configuration file of the codegen.

You can follow the plugin tips in Write Your Plugin, Validate Configuration and Using Visitor sections.

7. Test your plugin#

To test your plugin, create a test file - tests/plugin.spec.ts with the following content;

import { plugin } from '../src';
describe('My Plugin', () => {
const schema = buildSchema(/* GraphQL */ `
type Query {
foo: String!
it('Should greet', async () => {
const result = await plugin(schema, [], {
name: 'Dotan',
expect(result).toBe('Hello Dotan!');

Now, to make sure it works, run the following in your plugin directory:

yarn test

8. Integration#

You can also test the integration of your plugin with the codegen core and cli, the integration with other plugins and the output for some complex schemas and operations.

To do that, make sure everything is built by using yarn build in the root directory, then you can use it in ./dev-test/codegen.yml, and run yarn generate:examples in the project root directory, to run it.

9. Documentation#

GraphQL Code Generator website has API Reference for all our plugins, most of the documentation is generated from code, and some of it is written manually.

In order to add it to the website, do the following:

  1. Add JSDoc annotations to your config object, it can also include default value, examples and type:
export type MyPluginConfig = {
* @name name
* @description This allow you to generate a greeting with custom name
* @default anonymous
* @example Change the name
* ```yml
* generates:
* path/to/file.ts:
* plugins:
* - my-plugin
* config:
* name: Uri
* ```
name: string;

Now, open ./website/generate-config.js and add a record to the mapping in that filee, point the file with the configuration annotation, and the output file:

const mapping = {
'../packages/plugins/my-plugin/src/index.ts': BASE_DIR + '/',

Now, navigate to the website directory and run yarn generate:config-docs -this will take a minute, and it will generate the .md for all plugins. You should find your file under website/docs/generated-config directory.

Now, run yarn start to run the website. You markdown file is loaded, but it's not displayed yet, so let's create a new page for it first.

Create under website/docs/plugins/ and add the following content to it, and include the generated configuration API reference:

id: my-plugin
title: My Plugin
This is my new plugin.
Add here some custom instructions, explainations, installation guide and more.
{@import ../generated-config/}

Your plugin page should be available in: http://localhost:3000/docs/plugins/my-plugin

Now, just add it it to the website sidebar by updating website/sidebar.js file.

10. Add it to the live demo (optional)#

Our website has a live demo in the main page for most plugins, and you can add it there if you wish.

To add a new example to the live demo, start by making sure that your plugin package is available for the website:

  1. Edit website/package.json and add your plugin package under dependencies.
  2. Edit website/src/components/live-demo/plugins.js and add a mapping for the name of your plugin and it's package. This is required in order to have lazy loading and dynamic imports in our website.

Now, add your example under website/src/components/live-demo/examples.js - you can add a custom schema, documents and configuration.