Docs live reload is broken

[colebemis]

Describe the bug

Live reload is broken when running the docs site locally. Making changes to any markdown file results in this error message in the terminal:

error (intermediate value)(intermediate value)(intermediate value) is not iterable


  TypeError: (intermediate value)(intermediate value)(intermediate value) is not iterable
  
  - gatsby-webpack-eslint-graphql-schema-reload-plugin.ts:28 GatsbyWebpackEslintGraphqlSchemaReload.findEslintOptions
    [docs]/[gatsby]/src/utils/gatsby-webpack-eslint-graphql-schema-reload-plugin.ts:28:11
  
  - gatsby-webpack-eslint-graphql-schema-reload-plugin.ts:49 
    [docs]/[gatsby]/src/utils/gatsby-webpack-eslint-graphql-schema-reload-plugin.ts:49:28
  
  
  - Compiler.js:665 
    [docs]/[webpack]/lib/Compiler.js:665:23
  
  
  - Compiler.js:662 Compiler.compile
    [docs]/[webpack]/lib/Compiler.js:662:28
  
  - Watching.js:77 done
    [docs]/[webpack]/lib/Watching.js:77:18
  
  
  - start-webpack-server.ts:71 
    [docs]/[gatsby]/src/services/start-webpack-server.ts:71:5
  
  
  
  - index.js:173 watchRunHook
    [docs]/[webpack-virtual-modules]/index.js:173:5
  
  
  - Hook.js:154 AsyncSeriesHook.lazyCompileHook
    [docs]/[tapable]/lib/Hook.js:154:20
  
  - Watching.js:41 Watching._go
    [docs]/[webpack]/lib/Watching.js:41:32
  
  - Watching.js:169 Watching._invalidate
    [docs]/[webpack]/lib/Watching.js:169:9

To Reproduce
Steps to reproduce the behavior:

1. Run yarn in the root and docs directories
2. Run yarn develop in the docs directory
3. Save a change to any markdown file in the docs/content directory
4. Notice that the page doesn't reload and there is an error in the terminal

Expected behavior

Making a change to a markdown file should trigger a quick reload of localhost:8000 with the changes reflected on the page.

Video

https://www.loom.com/share/64492f6a228446d695ae75c0ed8f92d3?sharedAppSource=personal_library

Additional context

I ran git bisect and it appears the commit that introduced this error was f5c831d.

My guess is that the relevant change is the Gatsby upgrade in the yarn.lock file:

[colebemis]

Update: I also filed an issue in the Gatsby repo gatsbyjs/gatsby#28429