-
Notifications
You must be signed in to change notification settings - Fork 70
Incompatible graphql-language-service-utils #239
Comments
Same experience on our side...
solved by reverting to the last release which worked on our side (graphql-language-service-utils-1.0.18.tgz") |
ExecutableDefinitions.js doesn't exist until graphql 1.12.0, but https://github.com/graphql/graphql-language-service/blob/master/packages/utils/package.json allows 0.10.0 and up |
So, as far as I can tell, either we need to revert 068c57f or utils needs to drop peerdep support for graphql v0.10 and v0.11. Does that sound right? Pinging authors @divyenduz @asiandrummer – do you have any thoughts on this? Is there any precedent for when/how to drop support for older peerdeps? |
Hey folks — I ran into this again today. Any progress? |
v0.12 was released back in December so let's drop support for v0.11 (and below). This will require a major version bump for graphql-language-service (edit: I will do this) Could someone make a PR? |
Drop support for graphql v0.10 and v0.11 as these versions do not contain `ExecutableDefinitions` (required by packages/utils/src/validateWithCustomRules.js) N.b. this will require a major version bump at the next release. Fixes graphql#239
In npm, the current version of graphql-language-service-utils is 1.2.1 which seems to have issues when resolved transitively by the other older components.
Forcing graphql-language-service-utils to 1.2.0 resolves our build issue.
The text was updated successfully, but these errors were encountered: