Plugin-Sitemap | Statamic v1 plugin that generates a sitemap of your site | Sitemap 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:

It seems to be a known bug of the library, as you can see in the following GitHub threads:

• https://github.com/gatsbyjs/gatsby/issues/31167

• https://github.com/gatsbyjs/gatsby/issues/31095

That said, you can downgrade to version 3.30 which seems to be bug-free and be aware of using options.excludes instead of options.exclude (trailing "s") if you are excluding some pages.

Otherwise (and in the meantime) you can set the output path to / as a temporary workaround:

This is not a problem from your side. It is not a problem of package.json. In the ERR, the URL https://registry.npmjs.org/axios (last line of the error message) gives a JSON response which is flawed. See the below image. The JSON validation fails. They must resolve this.

Try running

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.

Didn't find a permanent solution, but found a fix...

The problem stemmed from a conflict between my gatsby-source-wordpress and the way my Polylang WP plugin gets exposed to the GraphQL API. Basically, the "Duplicate ID" is related to the first post the API could find that has a translation, and for some reason it breaks. As of this writing this seems to be specific to gatsby-source-wordpress version ^5.0.0 and ^5.1.0. My fix : revert to gatsby-source-wordpress version ^4.1.0-next.1, which does not suffer from the same issue.

This fix works for me with Gatsby v3.1.1.

The HTML on the question's page shows that the GIF images for figure 6(a) and 6(b) are not responsive.

Here is the HTML for figure 6(a):

What did you try so far? As @ksav pointed out, in this GitHub thread there are a several ways to fix a similar issue:

• Removing node_modules, .cache and install again
• Removing node_modules, .cache fix Gatsby to v2.23.3/upgrade up to ^2.26.1 where the bug is fixed and install again

It seems related to a loading staticQuery bug that can't be reproduced in a fresh install. The final trial is to remove your package-lock/yarn-lock.json and generate it again.

It has something to do with gatsby-remark-relative-images: "^2.0.2", the problem stopped happening when using version ^0.3.0 instead of ^2.0.2 or when using "gatsby-remark-relative-images-v2": "^0.1.5", instead. This is noted on their github page