Question 1

How to set up eslint-plugin-graphql with Apollo Client?

Accepted Answer

Set env to 'apollo' in your ESLint rule config, provide the schema via schemaJson or similar, and ensure queries use the 'gql' tag. The README includes detailed JavaScript config examples for this.

Question 2

eslint-plugin-graphql vs graphql-eslint: which one should I use?

Accepted Answer

For new projects, use graphql-eslint as it's community-supported and actively maintained, while eslint-plugin-graphql is being deprecated. Existing setups can still work but with limited updates.

Question 3

Why is Apollo deprecating eslint-plugin-graphql?

Accepted Answer

Apollo is focusing resources on other tools and recommends migrating to the community-supported graphql-eslint for better long-term maintenance, as noted in the deprecation warning in the README.

Question 4

How to lint standalone .graphql files with this plugin?

Accepted Answer

Set env to 'literal' in the ESLint rule and run eslint with extensions like --ext .js --ext .gql --ext .graphql to validate GraphQL literal files directly.

Question 5

Can eslint-plugin-graphql handle multiple GraphQL schemas?

Accepted Answer

Yes, by adding multiple configurations in the rule options with different tagNames and schemas, as shown in the 'Additional Schemas or Tags' section of the README.

Question 6

What if my GraphQL queries don't use a template tag?

Accepted Answer

You can use the 'fake-tag' package to create an identity tag, or wait for comment tag support which isn't implemented yet, making it a limitation for tag-less workflows.

eslint-plugin-graphql

What is eslint-plugin-graphql?

Overview

Use Cases

Best For

Related Projects

Found a gem we're missing?

Not Ideal For

Pros & Cons

Pros

Cons

Frequently Asked Questions