Issue with Deploying Gatsby Site on Netlify: Error Related to gatsby-source-wordpress Plugin and WPGraphQL

[sukantamajhi]

We are currently facing an issue when trying to deploy our website on Netlify. The issue persists even during local development with the gatsby develop and gatsby build commands. The problem appears to be related to the gatsby-source-wordpress plugin, even though we have updated it to the latest version (7.14). We are also using WPGraphQL version 2.0.0, which may be a part of the issue.

Steps to Reproduce:

• Set up the project with gatsby-source-wordpress plugin version 7.14.
• Run local development with gatsby develop or build the site using gatsby build.
• Try to deploy the site on Netlify.

Expected Behavior:

• The site should build and deploy without errors on Netlify, and the local development environment (gatsby develop) should run smoothly without issues.

Actual Behavior:

• We encounter errors during both local development and build, blocking us from deploying to Netlify.

Additional Information:

• We have ensured that the plugin is updated to the latest version (7.14).
• We are using WPGraphQL version 2.0.0.
• We are unable to proceed with development or deployment due to this issue.

Environment:

• gatsby-source-wordpress version: 7.14
• WPGraphQL version: 2.0.0
• Node version: 18.20.3
• Gatsby version: 5.13.5

Related Issues:

• gatsby-source-wordpress build fails when updating WP GraphQL to v2.0 #39231

[kylewebdev]

I'm getting the same issue

Environment:

• gatsby-source-wordpress: 7.15.0-next.1
• WPGraphQL version: 2.1.0
• Node version: 18.20.7
• Gatsby version: 5.14.0

[jrutheiser]

We're running into the same issue and had to downgrade WPGraphQL to 1.x.x which means no updates or security patches. It looks like the supported versions are hardcoded here: https://github.com/gatsbyjs/gatsby/blob/master/packages/gatsby-source-wordpress/src/supported-remote-plugin-versions.ts#L5 in the Gatsby plugin.

WPGraphQL has outlined breaking changes moving to v2 here https://www.wpgraphql.com/2024/12/16/wpgraphql-v2-0-technical-update-breaking-changes. These changes don't seem like much but doubtful we'll get a resolution here anytime soon unfortunately.

Gatsby clearly isn't a priority for Netlify ever since their takeover which is a shame. See #38696

[pieh]

[email protected] was released with changes to allow wp-graphql@2 and some more adjustments for breaking changes, specifically those 2:

• “category” field removal on errors: The “category” field has been removed from GraphQL error responses. If your application depends on this field, adjust your error-handling logic accordingly.
• debug entries moved: graphql-php now places debug information under the extensions key of the error response. Ensure your application properly handles this structure.

#39263 has full scope of changes