tqureshi-uog

We're having the *exact* same problem! Thank you for opening this issue. In our case, we notice it *doesn't* happen with one of our repositories that still uses Gatsby v5.11.0....

To clarify, we're *not* seeing the problem with Gatsby v5.11 - we *are* seeing the problem with the newer version, 5.12.6 Now that I look at your environment info, however,...

Here's my information for the repository where GraphiQL works: ``` System: OS: Linux 4.4 Ubuntu 22.04.3 LTS 22.04.3 LTS (Jammy Jellyfish) CPU: (8) x64 11th Gen Intel(R) Core(TM) i7-1185G7 @...

I believe I might have found a more consistent solution - upgrade GraphQL to v16.8.1 as per https://github.com/graphql/graphql-js/releases We were alerted about this update after activating dependabot on our repository....

We don't have it in our package.json either - it's a dependency of Gatsby itself, I believe. When dependabot created its automated PR, only our package-lock.json file changed.

I remain convinced it's due to a rogue dependency somewhere within Gatsby's implementation of GraphQL. Since I use npm, I'm not sure what the equivalent command is for yarn, but...