Error thrown in gatsby develop on file update

Description

When We run gatsby develop it starts without any problems, but when any file is updated, we get error stack trace in console and “Re-building development bundle” never ends.

Steps to reproduce

Unfortunately I could not reproduce this issue with any gatsby starter. In my project it happens every time I run gatsby develop.

Expected result

Re-building development bundle should end successfully.

Actual result

Error is thrown:

You can now view @site/app in the browser.
⠀
  http://localhost:8000/
⠀
View GraphiQL, an in-browser IDE, to explore your site's data and schema
⠀
  http://localhost:8000/___graphql
⠀
Note that the development build is not optimized.
To create a production build, use gatsby build
⠀
success Building development bundle - 85.687s
info added file at /home/user/repo/app/content/about/.goutputstream-ARI5O0
info changed file at /home/user/repo/app/content/about/nav.toml
info Imported navigation file has been changed: /home/user/repo/app/content/about/nav.toml
info file deleted at /home/user/repo/app/content/about/.goutputstream-ARI5O0
success createPages - 0.578s
success Checking for changed pages - 0.010s
success update schema - 0.092s
success onPreExtractQueries - 0.156s
success extract queries from components - 0.437s
success write out requires - 0.018s
success run static queries - 0.136s - 1/1 7.34/s

 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
    [APP]/[gatsby]/src/utils/gatsby-webpack-eslint-graphql-schema-reload-plugin.ts:28:11
  
  - gatsby-webpack-eslint-graphql-schema-reload-plugin.ts:49 
    [APP]/[gatsby]/src/utils/gatsby-webpack-eslint-graphql-schema-reload-plugin.ts:49:28
  
  
  - Compiler.js:665 
    [APP]/[webpack]/lib/Compiler.js:665:23
  
  
  - Compiler.js:662 Compiler.compile
    [APP]/[webpack]/lib/Compiler.js:662:28
  
  - Watching.js:77 done
    [APP]/[webpack]/lib/Watching.js:77:18
  
  
  - start-webpack-server.ts:69 
    [APP]/[gatsby]/src/services/start-webpack-server.ts:69:5
  
  
  
  - index.js:173 watchRunHook
    [APP]/[webpack-virtual-modules]/index.js:173:5
  
  
  - Hook.js:154 AsyncSeriesHook.lazyCompileHook
    [APP]/[tapable]/lib/Hook.js:154:20
  
  - Watching.js:41 Watching._go
    [APP]/[webpack]/lib/Watching.js:41:32
  
  - Watching.js:169 Watching._invalidate
    [APP]/[webpack]/lib/Watching.js:169:9
  
  - Watching.js:181 Watching.resume
    [APP]/[webpack]/lib/Watching.js:181:9
  
  - recompile.ts:23 
    [APP]/[gatsby]/src/services/recompile.ts:23:21
  
  - new Promise
  
  - recompile.ts:17 recompile
    [APP]/[gatsby]/src/services/recompile.ts:17:10
  
  - interpreter.js:721 Interpreter.exec
    [APP]/[xstate]/lib/interpreter.js:721:27
  
  - interpreter.js:223 Interpreter.execute
    [APP]/[xstate]/lib/interpreter.js:223:22
  
  - interpreter.js:243 Interpreter.update
    [APP]/[xstate]/lib/interpreter.js:243:18
  
  - interpreter.js:144 
    [APP]/[xstate]/lib/interpreter.js:144:23
  
  - scheduler.js:59 Scheduler.process
    [APP]/[xstate]/lib/scheduler.js:59:13
  
  - scheduler.js:43 Scheduler.schedule
    [APP]/[xstate]/lib/scheduler.js:43:14
  
  - interpreter.js:140 Interpreter.send
    [APP]/[xstate]/lib/interpreter.js:140:29
  
  - interpreter.js:825 
    [APP]/[xstate]/lib/interpreter.js:825:19
  
  - interpreter.js:301 Interpreter.update
    [APP]/[xstate]/lib/interpreter.js:301:21
  
  - interpreter.js:144 
    [APP]/[xstate]/lib/interpreter.js:144:23
  
  - scheduler.js:59 Scheduler.process
    [APP]/[xstate]/lib/scheduler.js:59:13
  
  - scheduler.js:43 Scheduler.schedule
    [APP]/[xstate]/lib/scheduler.js:43:14
  
  - interpreter.js:140 Interpreter.send
    [APP]/[xstate]/lib/interpreter.js:140:29
  
  - interpreter.js:836 actor.id
    [APP]/[xstate]/lib/interpreter.js:836:23
  

⠹ Re-building development bundle
not finished Re-building development bundle - 16.203s
^C^C

Environment

System:
    OS: Linux 5.3 Ubuntu 18.04.4 LTS (Bionic Beaver)
    CPU: (4) x64 Intel(R) Core(TM) i7-8650U CPU @ 1.90GHz
    Shell: 4.4.20 - /bin/bash
  Binaries:
    Node: 12.18.0 - /usr/bin/node
    npm: 6.9.0 - /usr/bin/npm
  Languages:
    Python: 2.7.17 - /usr/bin/python
  Browsers:
    Chrome: 83.0.4103.61
    Firefox: 76.0.1
  npmPackages:
    gatsby: ^2.24.6 => 2.24.44
    gatsby-plugin-catch-links: 2.0.13 => 2.0.13
    gatsby-plugin-create-client-paths: 2.0.5 => 2.0.5
    gatsby-plugin-less: 2.0.12 => 2.0.12
    gatsby-plugin-lunr: 1.5.2 => 1.5.2
    gatsby-plugin-matomo: 0.7.0 => 0.7.0
    gatsby-plugin-mdx: 1.2.6 => 1.2.6
    gatsby-plugin-nprogress: 2.0.10 => 2.0.10
    gatsby-plugin-page-creator: 2.1.5 => 2.1.5
    gatsby-plugin-react-helmet: 3.0.12 => 3.0.12
    gatsby-plugin-typescript: 2.0.13 => 2.0.13
    gatsby-plugin-webpack-bundle-analyzer: ^1.0.5 => 1.0.5
    gatsby-remark-autolink-headers: 2.0.16 => 2.0.16
    gatsby-remark-code-titles: 1.1.0 => 1.1.0
    gatsby-remark-copy-linked-files: 2.0.12 => 2.0.12
    gatsby-remark-custom-blocks: ^2.3.10 => 2.3.10
    gatsby-remark-embed-snippet: 3.2.4 => 3.2.4
    gatsby-remark-embed-video: 1.7.1 => 1.7.1
    gatsby-remark-emojis: 0.4.2 => 0.4.2
    gatsby-remark-prismjs: 3.5.3 => 3.5.3
    gatsby-source-elasticsearch: 0.1.0 => 0.1.0
    gatsby-source-filesystem: 2.0.33 => 2.0.33
    gatsby-transformer-json: 2.2.4 => 2.2.4
    gatsby-transformer-remark: 2.3.12 => 2.3.12
  npmGlobalPackages:
    gatsby-cli: 2.12.61

[caymanowy]

Hello,

I found a workaround for it. When I’ve added empty .eslintrc file in the root directory, hot reloading is working fine.

[eMachlo]

I guess we can close this ticket.