You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Feb 11, 2021. It is now read-only.
I'm actually using a Stack Overflow post to help push this forward, since it describes the issue and how a specific version only works (link below). The solution is to downgrade to "gatsby-source-prismic-graphql": "3.4.1-alpha.0".
In summary, when trying to query an imageSharp with newer versions of "gatsby-source-prismic-graphql" it will not work.
In my example, this would fail: query { prismic { home_page(uid: "home_page_slug", lang: "en-us") { background_home_image background_home_imageSharp { childImageSharp { fluid(quality: 100, maxWidth: 2000) { sizes } } } } } }
Once i downgraded to "gatsby-source-prismic-graphql": "3.4.1-alpha.0" it worked.
The text was updated successfully, but these errors were encountered:
Z11
changed the title
gatsby-source-prismic-graphql production build throws an error when querying for a sharp processed image
build throws an error when querying for an imageSharp image
Apr 30, 2020
I'm actually using a Stack Overflow post to help push this forward, since it describes the issue and how a specific version only works (link below). The solution is to downgrade to "gatsby-source-prismic-graphql": "3.4.1-alpha.0".
In summary, when trying to query an imageSharp with newer versions of "gatsby-source-prismic-graphql" it will not work.
In my example, this would fail:
query { prismic { home_page(uid: "home_page_slug", lang: "en-us") { background_home_image background_home_imageSharp { childImageSharp { fluid(quality: 100, maxWidth: 2000) { sizes } } } } } }
Once i downgraded to "gatsby-source-prismic-graphql": "3.4.1-alpha.0" it worked.
https://stackoverflow.com/questions/61176735/gatsby-source-prismic-graphql-production-build-throws-an-error-when-querying-for
The text was updated successfully, but these errors were encountered: