plugin-sass | Sass plugin for System.js | Plugin library

Your gatsby-node.js looks perfect. Your issue is caused by the types of the data context you are sending to the template (videoDetailTemplate). You are telling to GraphQL that both id and editorId are ID types while I guess they should be strings.

I guess changing this line:

I have it solved with:

Try to run npm install gatsby@latest And only after that run npm outdated

Assuming that your project builds correctly locally, this kind of issue is 99% related to mismatching versions of Node, so of the build dependencies installed in the end.

Run this command:

The structure for the new component when passing the image itself is using the image prop, not fluid. In addition, the query needs to fetch gatsbyImageData, not fluid as you can see in the docs:

There's not much debug in the question however, to me, it seems that you are using some dependencies outside React's scope, which may potentially block React's hydration process, which may explain the problem described. For example, using Leaflet instead of React's Leaflet or (depending on its implementation) Bootstrap instead of React's Boostrap.

You should be able to change all React-unfriendly modules to React's ones without too much effort and that should fix your problems.

Keep in mind that if your project "work in develop and breaks in build" doesn't mean that your project work or stops working, it just means that is working under certain and specific circumstances. Basically, and summarizing (to avoid extending the answer), gatsby develop uses the browser as an interpreter, where there are, among other things, global objects like window or document. However, gatsby build occurs in the Node server, where at the build time, there are not global objects because there are not even created yet, that the main reason why you may face a different behavior between both scenarios but doesn't mean that the project stopped working magically.

You can read further details in the Overview of Gatsby Build Process.

Another option, linked with blocking React's hydration, is that some component may be blocking that process because of its own behavior. Be careful when using global objects like window or document (or when importing modules that uses it), they use should be always be wrapped inside the following condition, as you can see from the docs:

When referencing window in a React component.

As mentioned in the comment by Eusbolh, you need to use relative path for the URL. E.g:

gatsby-plugin-sharp, according to the documentation:

• @babel/runtime
• async
• bluebird
• filenamify
• fs-extra
• gatsby-core-utils
• gatsby-telemetry
• got
• imagemin
• imagemin-mozjpeg
• imagemin-pngquant
• lodash
• mini-svg-data-uri
• potrace
• prob-image-size
• progress
• semver
• sharp
• svgo
• uuid
• Dev dependencies: @babel/cli, @babel/core, @types/sharp, babel-preset-gatsby-package, cross-env, gatsby-plugin-image, gatsby-plugin-utils

On the other side, mozjpeg has:

• bin-build
• bin-wrapper
• logalot
• Dev dependencies: ava, bin-check, compare-size, execa, tempy, xo

Import it like: