Skip to content
This repository was archived by the owner on Apr 8, 2025. It is now read-only.
This repository was archived by the owner on Apr 8, 2025. It is now read-only.

Unhandled error on spawning electron #277

@pascalkania

Description

@pascalkania

Hey,

i got an unhandled error on windows 10. You can see it in the following error message:

Date: 2019-11-15T07:09:30.232Z - Hash: 13443af1eec3ec91a112 - Time: 63205ms
** Angular Live Development Server is listening on localhost:4200, open your browser on http://localhost:4200/ **
i 「wdm」: Compiled successfully.
typescript compile success
events.js:187
      throw er; // Unhandled 'error' event
      ^

Error: spawn electron ENOENT
    at Process.ChildProcess._handle.onexit (internal/child_process.js:264:19)
    at onErrorNT (internal/child_process.js:456:16)
    at processTicksAndRejections (internal/process/task_queues.js:80:21)
Emitted 'error' event on ChildProcess instance at:
    at Process.ChildProcess._handle.onexit (internal/child_process.js:270:12)
    at onErrorNT (internal/child_process.js:456:16)
    at processTicksAndRejections (internal/process/task_queues.js:80:21) {
  errno: 'ENOENT',
  code: 'ENOENT',
  syscall: 'spawn electron',
  path: 'electron',
  spawnargs: [
    'C:\\Entwicklung\\projekte\\test-mono\\apps\\electron\\src\\electron',
    '--serve'
  ]
}

I think in the function startElectron (...) (dev-server\index.js - line 74) the wrong path of electron is determined.
It would be nice to prevent the start of electron over a command-line-argument e.g. --no-spawn

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions