You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Version 0.8.0 comes with this commit: 2f6313b which depends on the rules to be in the graphql package. However, the rules have only been renamed to have Rule suffix in this PR: graphql/graphql-js#2402 which is graphql@15.0.0
As a result, when I tried to run graphql-eslint with graphql@14.6.0, it failed because the rule file name is different.
Bumping to graphql@15.5.0 solved this issue for me.
Suggestions
Maybe we can update the peerDependencies to reflect this? ( I think that's what it's for right? )
Or maybe we could revert the commit that sets external rules for now? :)
The text was updated successfully, but these errors were encountered:
Hi @eddeee888
Tracking this in #292
It was a mistake, we fixed a bundling issue in the package, and now the graphql-js validation rules comes from node_modules, leading to an error in case of a new version of graphql.
Working on a fix :)
Bug description
Version 0.8.0 comes with this commit: 2f6313b which depends on the rules to be in the
graphql
package. However, the rules have only been renamed to haveRule
suffix in this PR: graphql/graphql-js#2402 which is graphql@15.0.0As a result, when I tried to run
graphql-eslint
with graphql@14.6.0, it failed because the rule file name is different.Bumping to graphql@15.5.0 solved this issue for me.
Suggestions
Maybe we can update the
peerDependencies
to reflect this? ( I think that's what it's for right? )Or maybe we could revert the commit that sets external rules for now? :)
The text was updated successfully, but these errors were encountered: