[Processor] '@graphql-eslint/graphql' was not found
See original GitHub issueI’m trying to configure the plugin with its processor following the config in the README.md file and I get the following error:
Error: ESLint configuration of processor in '.eslintrc.js#overrides[0]' is invalid: '@graphql-eslint/graphql' was not found.
Here is my config:
overrides: [
{
files: ['*.tsx', '*.ts', '*.jsx', '*.js'],
processor: '@graphql-eslint/graphql',
},
{
files: ['*.graphql'],
parser: '@graphql-eslint/eslint-plugin',
plugins: ['@graphql-eslint'],
rules: {},
},
],
Any advice would be appreciated 😃
Issue Analytics
- State:
- Created 3 years ago
- Reactions:8
- Comments:28 (5 by maintainers)
Top Results From Across the Web
[Processor] '@graphql-eslint/graphql' was not found · Issue #292
I'm trying to configure the plugin with its processor following the config in the README.md file and I get the following error: Error:...
Read more >typescript - @graphql-eslint/eslint-plugin errors - Stack Overflow
As the error states, "Query" and "Mutation" are not defined. It must first be defined before extending it, like so:
Read more >How to validate your GraphQL queries with ESLint
Get some quick tips for how to get syntax validation, schema validation, and highlighting working with GraphQL.
Read more >Linting GraphQL Schema and queries - Rule of Tech
Depending of you project structure and how you've created your schema and queries you can use different tools for linting it. eslint-plugin- ...
Read more >How not to learn GraphQL – The Guild
The term Anemic refers to a design where a Mutation (or Query) only contains data, not behaviors. A good GraphQL Schema design should:...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
This broke for me in v2.5.0. It worked in v2.4.0.
I’m using yarn v1 with
node_modules
, not berry.GraphQL: 15.7.0 ESLint: 8.2.0 Node.js: 14.18.1
EDIT: Somehow my dependencies in
node_modules
got installed in a weird way after trying this version which triggered the error above. After downgrading to v2.4.0, I was seeing the same error, which I hadn’t seen before. With a cleannode_modules
folder and a freshyarn
, the error does not present itself in either v2.4.0 nor v2.5.0.Thanks @B2o5T. I’m surprised the fix was so simple 😅 .