GraphQL-ESLint v4 Roadmap

[dimaMachina]

• Node 12/14/16 drop support [v4] drop support of Node.js 12/14/16, GraphQL 14/15 #1793
• Support ESLint 9, drop support for ESLint 7 and 8 (require at least 8.44) [v4] rule changes #1812
• Support GraphQL 17 [v4] drop support of Node.js 12/14/16, GraphQL 14/15 #1793
• Bundle to ESM only
• rename parserOptions.operations to parserOptions.documents to make consistency with graphql-config eslint plugin: parserOptions.operations doesn't work if skipGraphQLConfig is false #770 (comment) Please clarify that the graphql-config has precedence over options like ParserOptions.operations #1087

Was used a different approach #1795

• Remove GraphQLRuleTester from bundle and publish as @graphql-eslint/rule-tester Make graphql-config peer / optional dependency? #946 (comment) [v4] Remove GraphQLRuleTester from bundle #1792
• alphabetize changes
  • add definitions: true option for all config
  • rename values: ['EnumTypeDefinition'] to values: true, add variables: ['OperationDefinition', 'FragmentDefinition'] [v4] rule changes #1812
• bring back possible-type-extension to recommended config add new rules to recommended configs, rename relay config to schema-relay #1794
• Remove unique-enum-value-names rule, rename no-case-insensitive-enum-values-duplicates to unique-enum-value-names with new option caseSensitive Would it make sense to merge `no-case-insensitive-enum-values-duplicates` and `unique-enum-value-names`? #793 [v4] rule changes #1812
• Add unique-operation-name and unique-fragment-name rules to recommended config. add new rules to recommended configs, rename relay config to schema-relay #1794

The whole concept of sibling operations provided by parserOptions.operations or graphql-config's documents fields is based on uniquely named operations and fragments, for omitting false-positive/negative cases when operations and fragments are located in separated files. For this reason, these rules must be included in recommended config

• enable strict: true in tsconfig.json add "strict": true in tsconfig.json #1352
• known-directives remove ignoreClientDirectives in favour of graphql-config's extensions.customDirectives Support ignoreClientDirectives in operation definitions #1076 (comment)
• rename require-id-when-available to require-selections rule to require selecting __typename #1159 [v4] rule changes #1812
• remove requiring description for fields and add rootField: true to schema-recommended config [v4] rule changes #1812
• rename relay config to schema-relay add new rules to recommended configs, rename relay config to schema-relay #1794
• add spaced-comment to recommended config (has bugs with graphql language Rule Change: make spaced-comment language agnostic, add new option commentSymbol eslint/eslint#17145)

[vihangm]

Hey @dimaMachina are there any plans to publish a v4 release on npm?

[osdiab]

I also ask since the current version of graphql-eslint actually is causing vulnerability alerts for ws due to an old version of graphql-config. anything blocking the current alpha from being stable?

EDIT: looks like the published alpha version actually still has the vulnerable version, it was updated by Renovate but not in that release.