Chrome dev tools crashes on console type

• 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.

The program starts up, with dev tools open. All of the dev tools can be used but as soon as I type something the app crashes with no output on the console if using electon . but if I use npm start then therre is some output relating to chrome dev tools

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.

Put the console output here

What command line arguments are you passing?

electron-forge start

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

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

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.

After installing the Vue template by following the instructions as per website (Only difference the project named is VueTest2):

npm install -g electron-forge
electron-forge init my-new-project --template=vue
cd my-new-project
electron-forge start

Which gives me the output of :

[6976:0119/001536.330:ERROR:CONSOLE(7323)] "Extension server error: Object not found: <top>", source: chrome-devtools://devtools/bundled/inspector.js (7323)
npm ERR! code ELIFECYCLE
npm ERR! errno 3221225477
npm ERR! testvue2@1.0.0 start: `electron-forge start`
npm ERR! Exit status 3221225477
npm ERR!
npm ERR! Failed at the testvue2@1.0.0 start script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

npm ERR! A complete log of this run can be found in:
npm ERR!     C:\Users\Rehan\AppData\Roaming\npm-cache\_logs\2018-01-18T22_15_40_837Z-debug.log

The log file produced is as follows:

0 info it worked if it ends with ok
1 verbose cli [ 'C:\\Program Files\\nodejs\\node.exe',
1 verbose cli   'C:\\Program Files\\nodejs\\node_modules\\npm\\bin\\npm-cli.js',
1 verbose cli   'start' ]
2 info using npm@5.5.1
3 info using node@v8.9.3
4 verbose run-script [ 'prestart', 'start', 'poststart' ]
5 info lifecycle testvue2@1.0.0~prestart: testvue2@1.0.0
6 info lifecycle testvue2@1.0.0~start: testvue2@1.0.0
7 verbose lifecycle testvue2@1.0.0~start: unsafe-perm in lifecycle true
8 verbose lifecycle testvue2@1.0.0~start: PATH: C:\Program Files\nodejs\node_modules\npm\bin\node-gyp-bin;C:\Users\Rehan\Projects\Electron\TestVue2\node_modules\.bin;C:\ProgramData\Oracle\Java\javapath;C:\Program Files\Java\jdk1.8.0_151;C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Windows\System32\WindowsPowerShell\v1.0\;C:\Program Files\PuTTY\;C:\Program Files\nodejs\;C:\Users\Rehan\.dnx\bin;C:\Program Files\Microsoft DNX\Dnvm\;C:\Program Files\Microsoft SQL Server\120\Tools\Binn\;C:\Program Files\Microsoft SQL Server\130\Tools\Binn\;C:\Program Files\Git\cmd;C:\Program Files (x86)\NVIDIA Corporation\PhysX\Common;C:\Program Files\Amazon\AWSCLI\;%SystemRoot%\system32;%SystemRoot%;%SystemRoot%\System32\Wbem;%SYSTEMROOT%\System32\WindowsPowerShell\v1.0\;C:\Users\Rehan\AppData\Roaming\npm;C:\Android_SDK\newsdk\tools;C:\Android_SDK\newsdk\platform-tools;C:\Program Files\Java\jdk1.8.0_151;C:\Program Files\Gradle\gradle-4.4.1\bin;C:\OpenSSL\bin;C:\Program Files\Git\usr\bin\ssh.exe;C:\Users\Rehan\AppData\Local\Microsoft\WindowsApps;
9 verbose lifecycle testvue2@1.0.0~start: CWD: C:\Users\Rehan\Projects\Electron\TestVue2
10 silly lifecycle testvue2@1.0.0~start: Args: [ '/d /s /c', 'electron-forge start' ]
11 silly lifecycle testvue2@1.0.0~start: Returned: code: 3221225477  signal: null
12 info lifecycle testvue2@1.0.0~start: Failed to exec start script
13 verbose stack Error: testvue2@1.0.0 start: `electron-forge start`
13 verbose stack Exit status 3221225477
13 verbose stack     at EventEmitter.<anonymous> (C:\Program Files\nodejs\node_modules\npm\node_modules\npm-lifecycle\index.js:280:16)
13 verbose stack     at emitTwo (events.js:126:13)
13 verbose stack     at EventEmitter.emit (events.js:214:7)
13 verbose stack     at ChildProcess.<anonymous> (C:\Program Files\nodejs\node_modules\npm\node_modules\npm-lifecycle\lib\spawn.js:55:14)
13 verbose stack     at emitTwo (events.js:126:13)
13 verbose stack     at ChildProcess.emit (events.js:214:7)
13 verbose stack     at maybeClose (internal/child_process.js:925:16)
13 verbose stack     at Process.ChildProcess._handle.onexit (internal/child_process.js:209:5)
14 verbose pkgid testvue2@1.0.0
15 verbose cwd C:\Users\Rehan\Projects\Electron\TestVue2
16 verbose Windows_NT 10.0.14393
17 verbose argv "C:\\Program Files\\nodejs\\node.exe" "C:\\Program Files\\nodejs\\node_modules\\npm\\bin\\npm-cli.js" "start"
18 verbose node v8.9.3
19 verbose npm  v5.5.1
20 error code ELIFECYCLE
21 error errno 3221225477
22 error testvue2@1.0.0 start: `electron-forge start`
22 error Exit status 3221225477
23 error Failed at the testvue2@1.0.0 start script.
23 error This is probably not a problem with npm. There is likely additional logging output above.
24 verbose exit [ 3221225477, true ]

[malept]

This is a known issue in Electron 1.8.2-beta.3, and not a bug in Electron Forge. Please follow https://github.com/electron/electron/issues/11642 for updates. As a workaround, perhaps use the stable 1.7.x series.

[malept]

@cicely-f it probably doesn’t help that you’re specifying both electron and electron-prebuilt-compile, and that they’re contradictory versions.