chrome-devtools "Extension server error: Object not found: <top>"

• I have read the contribution documentation for this project.
• I agree to follow the code of conduct that this project follows, as appropriate.
• I have searched the issue tracker for an issue that matches the one I want to file, without success.

Please describe your issue:

The below warnings appears every time I start an electron instance with chome-devtools enabled. This is a similar issue to #664. It has no apparent effect on the behaviour of the app.

Console output when you run electron-forge with the environment variable DEBUG=electron-forge:*. (Instructions on how to do so here). Please include the stack trace if one exists.

The following is output approx 2 seconds after the electron window opens and each line appears in approx 1 second intervals.

[7496:0214/213940.214:ERROR:CONSOLE(7830)] "Extension server error: Object not found: <top>", source: chrome-devtools://devtools/bundled/shell.js (7830)
[7496:0214/213941.213:ERROR:CONSOLE(7830)] "Extension server error: Object not found: <top>", source: chrome-devtools://devtools/bundled/shell.js (7830)
[7496:0214/213942.213:ERROR:CONSOLE(7830)] "Extension server error: Object not found: <top>", source: chrome-devtools://devtools/bundled/shell.js (7830)
[7496:0214/213943.214:ERROR:CONSOLE(7830)] "Extension server error: Object not found: <top>", source: chrome-devtools://devtools/bundled/shell.js (7830)
[7496:0214/213944.214:ERROR:CONSOLE(7830)] "Extension server error: Object not found: <top>", source: chrome-devtools://devtools/bundled/shell.js (7830)
[7496:0214/213945.213:ERROR:CONSOLE(7830)] "Extension server error: Object not found: <top>", source: chrome-devtools://devtools/bundled/shell.js (7830)
[7496:0214/213946.214:ERROR:CONSOLE(7830)] "Extension server error: Object not found: <top>", source: chrome-devtools://devtools/bundled/shell.js (7830)

What command line arguments are you passing?

electron-forge start

What does your config.forge data in package.json look like?

    "forge": {
      "make_targets": {
        "win32": [
          "squirrel"
        ],
        "darwin": [
          "zip"
        ],
        "linux": [
          "deb",
          "rpm"
        ]
      },
      "electronPackagerConfig": {
        "packageManager": "npm"
      },
      "electronWinstallerConfig": {
        "name": "forge_react"
      },
      "electronInstallerDebian": {},
      "electronInstallerRedhat": {},
      "github_repository": {
        "owner": "",
        "name": ""
      },
      "windowsStoreConfig": {
        "packageName": "",
        "name": "forgereact"
      }
    }

Please provide either a failing minimal testcase (with a link to the code) or detailed steps to reproduce your problem. Using electron-forge init is a good starting point, if that is not the source of your problem.

Create a new electron-forge app using the ‘react’ template. Then start an instance with no modifications to code.

electron-forge init my-new-project --template=react
cd my-new-project
electron-forge start

[aplahitko]

After electron-forge init myapp --template=react I was having the same problem. s a boob, having found little to help online, I threw the following hail Mary and it worked.

npm install npm-check -g npm-check -u

using the last command above I interactively update all outdate packages to their latest versions and this error is gone now. In my case the updated packages were:

[npm-check] Update complete! [npm-check] react@16.8.6, react-dom@16.8.6, react-hot-loader@4.11.1, eslint@5.16.0, eslint-config-airbnb@17.1.0, eslint-plugin-jsx-a11y@6.2.1 [npm-check] You should re-run your tests to make sure everything works with the updates.

I hope this is helpful.

[malept]

I’m pretty sure it’s not. I searched GitHub and found this error in repos that do not use Electron Forge.