Skip to content
Discussion options

You must be logged in to vote

Just found the issue. We were manually overriding the version of graphql in our package.json, so it had nothing to do with this package. Sorry for the inconvenience!

Replies: 2 comments 2 replies

Comment options

You must be logged in to vote
2 replies
@garritfra
Comment options

@ardatan
Comment options

Comment options

You must be logged in to vote
0 replies
Answer selected by garritfra
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Category
Q&A
Labels
None yet
2 participants