gatsby: ERROR #85901 GRAPHQL

@darrencarlin Not ideal, but this probably happens if you have 0 assets/images - as a workaround you might try adding dummy image there (that you don’t have to use)

Hello again, sorry for the duplicate post, but I found a solution to the #85901 GRAPHQL error. Maybe this is helpful for others.

• I updated gatsby-transformer-sharp to 2.2.1.
• I removed sharp from the node_modules directory and re-installed it.
• I checked my dependencies via npm list sharp, updated the packages that were listed, including gatsby-plugin-sharp and gatsby-transformer-sharp, and now gatsby build is successful and all deployments on Netlify are working as before.

Now everything is working fine again. 😆 Thanks again guys. Hope this helps you

Thanks @kerminz Changing to those exact versions, without the caret in the version number, worked for me:

"gatsby-source-contentful": "2.0.41", and "gatsby": "2.9.10" rather than "gatsby-source-contentful": "^2.0.41", and "gatsby": "^2.9.10",

I tried using the versions with the caret but that didn’t help.

That will do for a temporary fix to get my site back updating until I work out a proper fix.

I am getting the same error when deploying my gatsby site on Netlify, none of the usual steps (npm install, deleting suspicious packages, clearing cache, …) fixed this…

12:48:51 PM: error #85901 GRAPHQL 12:48:51 PM: There was an error in your GraphQL query: 12:48:51 PM: Unknown type "ImageSharpFixed".

Getting the same error, too. However, I don’t have gatsby-plugin-mailchimp in my website

@pieh Amazing.

If anyone was wondering what they meant by “adding dummy image there”, follow these steps:

1. Login to Contenify
2. On the top navigation, select Media
3. Upload any asset (I uploaded a 100px by 100px white square)
4. Try rebuilding, and it just works

I have so many questions, but already wasted enough time on this to try to understand why that matters.

I can also confirm this is still an issue in version 2.13.x Downgrading Gatsby to strict version 2.9.10 seemed to temporarily fix the issue.

gatsby-plugin-algolia@0.3.1 is out with the fix! Thanks to @Haroenv ❤️

Spent an embarassing amount of time with this issue, when all it took to resolve was:

npm install gatsby-plugin-mailchimp@5.1.2

i ran npm outdated to see that gatsby-plugin-mailchimp was red and needed to be updated.

@pieh Amazing.

If anyone was wondering what they meant by “adding dummy image there”, follow these steps:

1. Login to Contenify
2. On the top navigation, select Media
3. Upload any asset (I uploaded a 100px by 100px white square)
4. Try rebuilding, and it just works

I have so many questions, but already wasted enough time on this to try to understand why that matters.

Thanks for this answer. I’m currently trying to do this, but when I attempt any image upload, getting “An error occurred while uploading your asset.”, no matter what image I upload. Hopefully contentful will resolve that very soon. ( might be a corporate firewall though, too,… so I’m going to try connecting to their guest wifi here ). Edit: dang, that was it. ( shouldn’t be working on their time anyway )

It happens when you use contentful as your CMS, as it forcefully creates image asset in the node modules folder. one needs to add a dummy image to the Media section in the contentful web application, further, if there are image manipulation plugins like gatsby-transformer-remark, gatsby-plugin-sharp or similar, you need to take care of that, as gatsby throws an exception by default in the most newer versions !!

I’m having this issue on Gatsby@2.13+ also, same as @andrewlsimplisafe I went back to Gatsby@2.12 and all ok, for now.

T.Hanks

@andrewlsimplisafe I can use up to Gatsby 2.11.7 and avoid this error.

Also, I use none of the plugins mentioned above:

  System:
    OS: macOS 10.14.5
    CPU: (4) x64 Intel(R) Core(TM) i5-5287U CPU @ 2.90GHz
    Shell: 3.2.57 - /bin/bash
  Binaries:
    Node: 11.6.0 - ~/.nvm/versions/node/v11.6.0/bin/node
    Yarn: 1.12.3 - ~/.nvm/versions/node/v11.6.0/bin/yarn
    npm: 6.5.0-next.0 - ~/.nvm/versions/node/v11.6.0/bin/npm
  Languages:
    Python: 2.7.10 - /usr/bin/python
  Browsers:
    Chrome: 75.0.3770.100
    Firefox: 67.0.4
    Safari: 12.1.1
  npmPackages:
    gatsby: ^2.11.7 => 2.11.7
    gatsby-image: ^2.2.4 => 2.2.4
    gatsby-link: ^2.2.0 => 2.2.0
    gatsby-plugin-gtag: ^1.0.11 => 1.0.11
    gatsby-plugin-mailchimp:
https://github.com/benjaminhoffman/gatsby-plugin-mailchimp.git#gatsby-v2 =>
3.3.0
    gatsby-plugin-manifest: ^2.2.1 => 2.2.1
    gatsby-plugin-offline: ^2.2.0 => 2.2.0
    gatsby-plugin-react-helmet: ^3.1.0 => 3.1.0
    gatsby-plugin-react-helmet-canonical-urls: ^1.2.0 => 1.2.0
    gatsby-plugin-remove-serviceworker: ^1.0.0 => 1.0.0
    gatsby-plugin-remove-trailing-slashes: ^2.1.0 => 2.1.0
    gatsby-plugin-sass: ^2.1.0 => 2.1.0
    gatsby-plugin-sharp: ^2.2.2 => 2.2.2
    gatsby-plugin-sitemap: ^2.2.1 => 2.2.1
    gatsby-plugin-webpack-bundle-analyzer: ^1.0.5 => 1.0.5
    gatsby-source-filesystem: ^2.1.2 => 2.1.2
    gatsby-source-prismic: ^2.2.0 => 2.2.0
    gatsby-transformer-sharp: ^2.2.1 => 2.2.1
    gatsby-transformer-sqip: 2.1.4 => 2.1.4

am getting the same error when deploying my gatsby site on Netlify, none of the usual steps (npm install, deleting suspicious packages, clearing cache, …) fixed this…

12:48:51 PM: error #85901 GRAPHQL 12:48:51 PM: There was an error in your GraphQL query: 12:48:51 PM: Unknown type "ImageSharpFixed".

@spookyMilly This should be fixed by updating gatsby-transformer-sharp to 2.2.1

This is occurring because some packages happen to ship example code (that includes queries). And we now parse node_modules to support queries in dependencies and themes since https://github.com/gatsbyjs/gatsby/pull/15284

The correct fix for this is for packages to add examples to .npmignore

I’m fixing gatsby-plugin-mailchimp and gatsby-plugin-algolia right now and writing a script to find more plugins in the wild that need to the resolved.

In the mean time, @javidhsueh @bogdancss @spookyMilly can you please post your gatsby info results so we can find the packages that are causing this for you and fix!

Edit: Fixes for gatsby-plugin-mailchimp and gatsby-plugin-algolia are open in https://github.com/benjaminhoffman/gatsby-plugin-mailchimp/pull/40 and https://github.com/algolia/gatsby-plugin-algolia/pull/31