Question 1

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

Accepted Answer

Install the plugin via npm, then add a rule in your .eslintrc.js with env set to 'apollo' and provide your schema using schemaJson, schemaJsonFilepath, or schemaString, as detailed in the Apollo config example in the README.

Question 2

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

Accepted Answer

Given eslint-plugin-graphql's deprecation warning, graphql-eslint is the recommended choice for new projects as it's community-supported and actively maintained, though eslint-plugin-graphql still works if you're already integrated.

Question 3

Can I lint standalone .graphql files with this plugin?

Accepted Answer

Yes, by setting env to 'literal' in your ESLint config and extending eslint to check .gql or .graphql file extensions, as shown in the literal files example in the README.

Question 4

How to handle multiple GraphQL schemas in one project?

Accepted Answer

Append additional config objects to the rule with different tagName and schemaJson settings, allowing validation against multiple schemas, demonstrated in the 'Additional Schemas or Tags' section of the README.

Question 5

Why does eslint-plugin-graphql fail with eslint --cache?

Accepted Answer

Using schemaJsonFilepath is incompatible with eslint --cache due to how file paths are resolved; opt for schemaJson or schemaString instead to avoid caching issues, as noted in the common options.

Question 6

How to enforce named operations in GraphQL queries?

Accepted Answer

Use the graphql/named-operations rule separately in your ESLint config, specifying your schema to ensure all operations have names, improving debugging and server logs.

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