Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Unhandled 'error' event

See original GitHub issue

The CI server(TeamCity) that I am using is behind a proxy. When I run %lhci% collect --url="https://xxx/"
I got the below error message:

Running Lighthouse 3 time(s) on https://xxx/
  events.js:292
        throw er; // Unhandled 'error' event
        ^
  Error: spawn node ENOENT
      at Process.ChildProcess._handle.onexit (internal/child_process.js:267:19)
      at onErrorNT (internal/child_process.js:469:16)
      at processTicksAndRejections (internal/process/task_queues.js:84:21)
  Emitted 'error' event on ChildProcess instance at:
      at Process.ChildProcess._handle.onexit (internal/child_process.js:273:12)
      at onErrorNT (internal/child_process.js:469:16)
      at processTicksAndRejections (internal/process/task_queues.js:84:21) {
    errno: 'ENOENT',
    code: 'ENOENT',
    syscall: 'spawn node',
    path: 'node',
    spawnargs: [
      'D:\\storage\\TOOLs\\Node\\12.18.2\\node_modules\\@lhci\\cli\\node_modules\\lighthouse\\lighthouse-cli\\index.js',
      'https://staging-web.ccleaner.com/',
      '--output',
      'json',
      '--output-path',
      'stdout',
      '--cli-flags-path',
      'D:\\work\\d861189cd355c9e2\\.lighthouseci\\flags-33da5e9f-3beb-41da-86c0-a859580f8d85.json'
    ]
  }

I also have environment variables for proxy: HTTP_PROXY, HTTP_PROXY_HOST and HTTP_PROXY_PORT Any idea what the error really is about?