Bug inwhen used withabout gatsby-typescript

[d4rekanguok]

Bug in [email protected] when used with [email protected]

[d4rekanguok]

Hey @kaleabmelkie, thank you again for providing a reproduction!

I think it boils down to incompatible issue with the graphql version Gatsby uses — I'm not sure what we can do here until Gatsby upgrades to graphql 15 :(.

If you happen to use yarn, pinning Gatsby's graphql version to 14.6 seem to resolve the issue:

in package.json

{
  "resolutions": {
    "gatsby/graphql": "14.6.0"
  }
}

Though yarn resolution seems to be a little flaky. I fount it to work more consistently if I nuke node_modules and run yarn again after specifying new resolutions.

Hope it helps — I'll keep this issue open.

[d4rekanguok]

Ooh very interesting, thank you for opening an issue! I'll try to fix this

[d4rekanguok]

Thanks, that's solid! I've found this error:

failed We've encountered an error: Objects are not valid as
a React child
(found: GraphQLDocumentError: GraphQLDocumentError: Fragment
"GatsbyImageSharpFixed" is never used.). If you meant to render a collection of
children, use an array instead.

Will go from there

[d4rekanguok]

Hey @kaleabmelkie, I was unable to reproduce this error. Do you have a sample project I can use? It seems like latest version of Gatsby has yet to use graphql 15 & when I force with yarn resolution, it just choked. I must have missing something.

Nevertheless I've upgraded all our dependencies to supports graphql 15, would you give it a try to see if it fixes the error? ([email protected])

[kaleabmelkie]

With v2.7.1 (and [email protected]) it logs a similar (but smaller) error on the console, but it actually launches the app and it works fine.

Here is a sample project:

https://codesandbox.io/s/frosty-neumann-uou9z

(Fork and restart it, if you want to see the error on console)