[gatsby-source-contentful] GraphQL can't identify contentful page type after migrating to Gatsby v3

[OfficePop]

Description

Gatsby is failing to compile a project with both npm run develop and npm run build after migrating from V2 to V3.

Here is the structure of the graphql query in gatsby-node.js that is used to fetch initial page data:

        graphql(`
        query allTypesOfPages {
            guideTopicPages: allContentfulTechNote {
                edges {
                  node {
                    title
                    topicSlug
                  }
                }
            }
            rulePages: allRulesJson {
                edges {
                    node {
                        rulename
                    }
                }
            }
            apiReferences: allContentfulApiGuideRichText {
                edges {
                  node {
                    title
                    topicSlug
                  }
                }
            }
            whatsnew: allContentfulWhatsNew {
                edges {
                    node {
                    id
                    body {
                        content {
                            content {
                                value
                            }
                        }
                    }
                    title
                    }
                }
            }
        }
        `)

This work without issue on v2, but after upgrading to v3 and settling all dependencies any build attempt throws this error:

 ERROR #85923  GRAPHQL

There was an error in your GraphQL query:

Cannot query field "content" on type "ContentfulWhatsNewBody".

If you don't expect "content" to exist on the type "ContentfulWhatsNewBody" it is most likely a typo.
However, if you expect "content" to exist there are a couple of solutions to common problems:

- If you added a new data source and/or changed something inside gatsby-node.js/gatsby-config.js, please try a restart of your
development server
- The field might be accessible in another subfield, please try your query in GraphiQL and use the GraphiQL explorer to see which
fields you can query and what shape they have
- You want to optionally use your field "content" and right now it is not used anywhere. Therefore Gatsby can't infer the type and
add it to the GraphQL schema. A quick fix is to add at least one entry with that field ("dummy content")

It is recommended to explicitly type your GraphQL schema if you want to use optional fields. This way you don't have to add the
mentioned "dummy content". Visit our docs to learn how you can define the schema for "ContentfulWhatsNewBody":
https://www.gatsbyjs.com/docs/reference/graphql-data-layer/schema-customization#creating-type-definitions

File: gatsby-node.js:14:12

Steps to reproduce

1. Create a site with a similar graphQL query to whatsnew.
2. Attempt to build with Gatsbyv3.

Expected result

The site should build normally.

Actual result

Type inference doesn't work for all page queries after migrating to GatsbyV3.

Environment

  System:
    OS: macOS 11.4
    CPU: (12) x64 Intel(R) Core(TM) i7-9750H CPU @ 2.60GHz
    Shell: 3.2.57 - /bin/bash
  Binaries:
    Node: 14.15.2 - /usr/local/bin/node
    Yarn: 1.22.10 - /usr/local/bin/yarn
    npm: 7.13.0 - /usr/local/bin/npm
  Languages:
    Python: 2.7.16 - /usr/bin/python
  Browsers:
    Chrome: 91.0.4472.106
    Firefox: 84.0.1
    Safari: 14.1.1
  npmPackages:
    gatsby: ^3.7.2 => 3.7.2
    gatsby-image: ^3.7.1 => 3.7.1
    gatsby-plugin-image: ^1.7.1 => 1.7.1
    gatsby-plugin-offline: ^4.7.1 => 4.7.1
    gatsby-plugin-react-helmet: ^4.7.1 => 4.7.1
    gatsby-plugin-sharp: ^3.7.1 => 3.7.1
    gatsby-plugin-styled-components: ^4.7.1 => 4.7.1
    gatsby-plugin-typography: ^3.7.1 => 3.7.1
    gatsby-source-contentful: ^5.7.1 => 5.7.1
    gatsby-source-filesystem: ^3.7.1 => 3.7.1
    gatsby-transformer-json: ^3.7.1 => 3.7.1
    gatsby-transformer-remark: ^4.1.0 => 4.1.0
    gatsby-transformer-sharp: ^3.7.1 => 3.7.1
  npmGlobalPackages:
    gatsby-cli: 3.0.0

If it helps, here is the Gatsby v2 environment the site builds correctly under:

  System:
    OS: macOS 11.4
    CPU: (12) x64 Intel(R) Core(TM) i7-9750H CPU @ 2.60GHz
    Shell: 3.2.57 - /bin/bash
  Binaries:
    Node: 14.15.2 - /usr/local/bin/node
    Yarn: 1.22.10 - /usr/local/bin/yarn
    npm: 7.13.0 - /usr/local/bin/npm
  Languages:
    Python: 2.7.16 - /usr/bin/python
  Browsers:
    Chrome: 91.0.4472.106
    Firefox: 84.0.1
    Safari: 14.1.1
  npmPackages:
    gatsby: ^2.15.6 => 2.15.6
    gatsby-image: ^2.2.17 => 2.2.17
    gatsby-plugin-offline: ^2.2.10 => 2.2.10
    gatsby-plugin-react-helmet: ^3.1.6 => 3.1.6
    gatsby-plugin-styled-components: ^3.1.5 => 3.1.5
    gatsby-plugin-typography: ^2.3.7 => 2.3.7
    gatsby-source-contentful: ^2.1.32 => 2.1.32
    gatsby-source-filesystem: ^2.1.21 => 2.1.21
    gatsby-transformer-json: ^2.2.8 => 2.2.8
    gatsby-transformer-remark: ^4.1.0 => 4.1.0
  npmGlobalPackages:
    gatsby-cli: 3.0.0

[LekoArts]

You've also updated the contentful source plugin by a couple of major versions so you'll also need to account for any breaking changes there. This is most likely your problem.

For example here's a thread of people talking about the Rich Text changes: #28098