Develop/Build fails on `extracting-queries` with latest Gatsby (glob 7.2.2)

[linfordbacon-ngenius]

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

When attempting to use the YARN package manager, the gatsby develop server fails on the extract queries from components step with the error message:

Missing onError handler for invocation 'extracting-queries', error was 'TypeError: Cannot read properties of undefined (reading 'charAt')'. Stacktrace was 'TypeError: Cannot read properties of undefined
(reading 'charAt')

Reproduction Link

https://www.gatsbyjs.com/docs/tutorial/part-1/

Steps to Reproduce

1. Install gatesby
2. run gatesby new
3. select 'yarn' as package manager (or ensure you have set this previously)
4. run gatesby develop
5. observe error

Expected Result

Several things:

1. gatesby development server should start
2. gatesby should provide a more useful error message

Actual Result

Missing onError handler for invocation 'extracting-queries', error was 'TypeError: Cannot read properties of undefined (reading 'charAt')'. Stacktrace was 'TypeError: Cannot read properties of undefined        
(reading 'charAt')
    at GlobSync._processReaddir (C:\Users\...\gatsby test\gatsby_yarn\node_modules\glob\sync.js:148:35)
    at GlobSync._process (C:\Users\...\gatsby test\gatsby_yarn\node_modules\glob\sync.js:132:10)
    at new GlobSync (C:\Users\...\gatsby test\gatsby_yarn\node_modules\glob\sync.js:45:10)
    at Function.sync (C:\Users\...\gatsby test\gatsby_yarn\node_modules\glob\sync.js:23:10)
    at reduce (C:\Users\...\gatsby test\gatsby_yarn\node_modules\gatsby\src\query\query-compiler.js:128:15)
    at Array.reduce (<anonymous>)
    at parseQueries (C:\Users\...\gatsby test\gatsby_yarn\node_modules\gatsby\src\query\query-compiler.js:126:5)
    at compile (C:\Users\...\gatsby test\gatsby_yarn\node_modules\gatsby\src\query\query-compiler.js:65:25)
    at updateStateAndRunQueries (C:\Users\...\gatsby test\gatsby_yarn\node_modules\gatsby\src\query\query-watcher.ts:223:40)
    at extractQueries (C:\Users\...\gatsby test\gatsby_yarn\node_modules\gatsby\src\services\extract-queries.ts:18:3)'

⠙ extract queries from components

Environment

System:
    OS: Windows 10 10.0.22000
    CPU: (16) x64 AMD Ryzen 7 5700G with Radeon Graphics         
  Binaries:
    Node: 18.1.0 - C:\Program Files\nodejs\node.EXE
    Yarn: 1.22.15 - C:\Program Files\nodejs\yarn.CMD
    npm: 8.8.0 - C:\Program Files\nodejs\npm.CMD
  Languages:
    Python: 3.10.4
  Browsers:
    Edge: Spartan (44.22000.120.0), Chromium (101.0.1210.39)
  npmPackages:
    gatsby: ^4.14.0 => 4.14.0 
    gatsby-plugin-emotion: ^7.14.0 => 7.14.0 
  npmGlobalPackages:
    gatsby-cli: 4.14.0

Config Flags

No

[barbalex]

I ran into the exact same issue after updating gatsby from v4.13.1 to 4.14.0.
Am using yarn but do not know if that has an influence.
After having this happen I downgraded gatsby and a dozen plugis again but can still not get my project working again 😢

[linfordbacon-ngenius]

Yeah, same. It seems like you end up in a completely unrecoverable state.

You could try gatsby clean but that didn’t work for me.

One thing I forgot to mention is that I’m using the emotion plug-in but I really don’t think that’s the culprit.

[yolomep]

yeah I have the same issue. Probably should not have updated gatsby cli.

[draghia-andrei]

Same issue after updating gatsby from v4.13.1 to 4.14.0.
I am using "npm" and also Windows OS.
Version of "glob" library is 7.2.2
gatsby clean didn't` fix it.

Late Edit:
Managed to get it fixed by putting this in my package.json

  "overrides": {
    "glob": "7.2.0"
  },

Essentially using an older version of this transitive dependency.

[duongthaicuong]

Yeah, same
"gatsby": "^3.8.1"

[djwinston]

@draghia-andrei Thanks. You right.
gatsby 4.13.0 has devDependencies "glob": "^7.1.7".
gatsby 4.14.0 has devDependencies "glob": "^7.2.0" , so ^ installed glob 7.2.2 which published a day ago

I guess to overrides glob only for gatsby
"overrides": { "gatsby": { "glob": "7.2.0" } }

[Alexyoe]

Same issue. Glob fix doesn't seem to help.
"gatsby": "^4.12.1"

Edit:
Thanks @djwinston for the advice. It seems to be working now. Weirdly, I need to run development before build or it fails now.

[djwinston]

@Alexyoe

Same issue. Glob fix doesn't seem to help. "gatsby": "^4.12.1"

Did you try to remove node_modules package-lock.json and reinstall packages with overrides section ? Probably package-lock.json has gatsby 4.14.0 and glob 7.2.2 because record "^4.12.1" means that package manager can install latest minor version
Also you can find installed version of package in package-lock.json or npm view gatsby version

[M4ss1ck]

Hi.
I'm using pnpm and getting the exact same error. Setting "overrides" in package.json didn't work for me.
It's a fresh install: I did pnpm init gatsby, then pnpm i and I'm getting this error with gatsby develop and gatsby build

[mbrinkl]

I had to update npm to get the "overrides" to work properly. As per this issue ( npm/cli#4322 ) it should work properly as of npm@8.6.0. That fixed it for me.

[djwinston]

@M4ss1ck Exactly. overrides introduced in config of package.json v8.x npm v8.x and this solution related to author issue

my environment

gatsby info

  System:
    OS: Windows 10 10.0.22000
    CPU: (16) x64 11th Gen Intel(R) Core(TM) i7-11800H @ 2.30GHz
  Binaries:
    Node: 16.15.0 - C:\Program Files\nodejs\node.EXE
    Yarn: 1.22.18 - C:\Program Files\nodejs\yarn.CMD
    npm: 8.5.5 - C:\Program Files\nodejs\npm.CMD
  Languages:
    Python: 3.10.2
  Browsers:
    Edge: Spartan (44.22000.120.0), Chromium (101.0.1210.47)
  npmPackages:
    gatsby: ^4.14.0 => 4.14.0
    gatsby-plugin-image: ^2.14.1 => 2.14.1
    gatsby-plugin-manifest: ^4.14.0 => 4.14.0
    gatsby-plugin-react-helmet: ^5.14.0 => 5.14.0
    gatsby-plugin-sass: ^5.14.0 => 5.14.0
    gatsby-plugin-sharp: ^4.14.1 => 4.14.1
    gatsby-plugin-sitemap: ^5.14.0 => 5.14.0
    gatsby-source-filesystem: ^4.14.0 => 4.14.0
    gatsby-transformer-sharp: ^4.14.0 => 4.14.0
  npmGlobalPackages:
    gatsby: 4.14.0

[sea-sol]

Same issue, is there any solution for this error?
I have fixed this issue by downgrade of gatsby. (even it can't be called good way), I hope someone deploy correct and smart way.

here is what I did.
"gatsby": "^3.9.1",
"gatsby-link": "^3.9.0",
"gatsby-plugin-google-gtag": "^3.9.0",
"gatsby-plugin-image": "^1.14.1",
"gatsby-plugin-layout": "^2.9.0",
"gatsby-plugin-manifest": "^3.9.0",
"gatsby-plugin-module-resolver": "^1.0.3",
"gatsby-plugin-react-helmet": "^4.9.0",
"gatsby-plugin-react-svg": "^3.0.1",
"gatsby-plugin-sass": "^4.9.0",
"gatsby-plugin-sharp": "^3.14.1",
"gatsby-react-router-scroll": "^4.9.0",
"gatsby-source-filesystem": "^3.14.0",
"gatsby-transformer-sharp": "^3.14.0",
"gatsby-plugin-postcss": "^4.9.0",

(npm install after clear package.lock and node_module,)

[linfordbacon-ngenius]

So I've tried out the glob override fixed proposed by @draghia-andrei (thanks!) and that seems to work well.

I'll update the name of the issue as it doesn't seem to be Yarn related (although using yarn/ pnpm seems to break the build immediately from gatsby new whereas using npm seems to work until you add additional dependencies)