gatsby: 4.15: Gatsby Script causing existing Jest tests to fail

Preliminary Checks

• This issue is not a duplicate. Before opening a new issue, please search existing issues: https://github.com/gatsbyjs/gatsby/issues
• This issue is not a question, feature request, RFC, or anything other than a bug report directly related to Gatsby. Please post those things in GitHub Discussions: https://github.com/gatsbyjs/gatsby/discussions

Description

Running on working version of 4.14.1, then updating to Gatsby 4.15.0 (and updating all other gatsby-* versions likewise) causes a working Gatsby install which includes Jest to fail for some tests due to gatsby-script, even if there is no direct use of the <Script> tag.

Error returns is:

 ● Test suite failed to run

    Jest encountered an unexpected token

    Jest failed to parse a file. This happens e.g. when your code or its dependencies use non-standard JavaScript syntax, or when Jest is not configured to support such syntax.

    Out of the box Jest supports Babel, which will be used to transform your files into valid JS based on your Babel configuration.

    By default "node_modules" folder is ignored by transformers.

    Here's what you can do:
     • If you are trying to use ECMAScript Modules, see https://jestjs.io/docs/ecmascript-modules for how to enable it.
     • If you are trying to use TypeScript, see https://jestjs.io/docs/getting-started#using-typescript
     • To have some of your "node_modules" files transformed, you can specify a custom "transformIgnorePatterns" in your config.
     • If you need a custom transformation specify a "transform" option in your config.
     • If you simply want to mock your non-JS modules (e.g. binary assets) you can stub them out with the "moduleNameMapper" config option.

    You'll find more details and examples of these config options in the docs:
    https://jestjs.io/docs/configuration
    For information about custom transformations, see:
    https://jestjs.io/docs/code-transformation

    Details:

    /Users/MYNAME/site/node_modules/gatsby-script/dist/index.js:1
    ({"Object.<anonymous>":function(module,exports,require,__dirname,__filename,jest){export * from "./gatsby-script";
                                                                                      ^^^^^^

    SyntaxError: Unexpected token 'export'

      at Runtime.createScriptFromCode (node_modules/jest-runtime/build/index.js:1773:14)
      at Object.require (node_modules/gatsby/cache-dir/commonjs/gatsby-browser-entry.js:45:21)

Reproduction Link

none yet

Steps to Reproduce

Have a working 4.14.1 Gatsby site up and working, including jest tests Upgrade to 4.15.0

Expected Result

4.15.0 is a dropin replacement, or there is documentation on what needs to change

Actual Result

Errors on most, but not all tests.

Environment

Binaries:
    Node: 16.15.0 - ~/.nvm/versions/node/v16.15.0/bin/node
    npm: 8.10.0 - ~/.nvm/versions/node/v16.15.0/bin/npm
  Browsers:
    Chrome: 101.0.4951.64
    Safari: 15.5
  npmPackages:
    gatsby: ^4.15.0 => 4.15.0
    gatsby-image: ^3.11.0 => 3.11.0
    gatsby-link: ^4.15.0 => 4.15.0
    gatsby-plugin-canonical-urls: ^4.15.0 => 4.15.0
    gatsby-plugin-google-fonts: ^1.0.1 => 1.0.1
    gatsby-plugin-google-gtag: ^4.15.0 => 4.15.0
    gatsby-plugin-html-attributes: ^1.0.5 => 1.0.5
    gatsby-plugin-manifest: ^4.15.0 => 4.15.0
    gatsby-plugin-netlify: ^4.4.0 => 4.4.0
    gatsby-plugin-offline: ^5.15.0 => 5.15.0
    gatsby-plugin-purgecss: ^6.1.2 => 6.1.2
    gatsby-plugin-robots-txt: ^1.7.1 => 1.7.1
    gatsby-plugin-sharp: ^4.15.0 => 4.15.0
    gatsby-plugin-sitemap: ^5.15.0 => 5.15.0
    gatsby-plugin-styled-components: ^5.15.0 => 5.15.0
    gatsby-source-filesystem: ^4.15.0 => 4.15.0
    gatsby-transformer-sharp: ^4.15.0 => 4.15.0

Config Flags

no