-
Notifications
You must be signed in to change notification settings - Fork 75
Cannot use GraphQLDirective "@include" from another module or realm #176
Comments
I'm also experiencing this issue. It seems like it's a dependency issue with gatsby-source-graphql-universal, another issue here. |
Me, too. I just posted an issue: birkir/gatsby-source-graphql-universal#14 A workaround is to add a resolution to your package.json. |
Adding a resolution to package.json worked! Like this: "resolutions": {
"graphql": "14.6.0"
} |
I can also confirm this solution works |
Same error here. Unfortunately the proposed solution of:
Did not work for me :/
I tried removing node modules + cache and installing from scratch and had the same result. My full runtime package list is as follows:
|
I have opened an issue in gatsby-source-graphql-universal. The problem is not with this project. It might be more helpful to the maintainer if we post our reports over there. Not a huge deal, but for those adding the resolution, to remain in sync with Gatsby I'd recommend including the carat as described in the other issue:
|
try |
Facing this issue:
Using version 3.5.0
The text was updated successfully, but these errors were encountered: