Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Crashing when launching Chrome debugger #760

Open
endquote opened this issue Feb 10, 2021 · 0 comments
Open

Crashing when launching Chrome debugger #760

endquote opened this issue Feb 10, 2021 · 0 comments

Comments

@endquote
Copy link

I have a Haul project, and am able to turn on debugging such that Haul launches Chrome and lets me debug. This is great.

If instead I run my project in a VScode devcontainer, Chrome isn't available. Haul tries to launch Chrome, fails, and crashes:

error ▶︎ Error: spawn google-chrome 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:77:11) {
  errno: 'ENOENT',
  code: 'ENOENT',
  syscall: 'spawn google-chrome',
  path: 'google-chrome',
  spawnargs: [ 'http://mymachine:8081/debugger-ui' ]}

Looking at launchBrowser.ts, it seems like it should print the URL to navigate to manually, which would be great. But maybe that code path isn't being triggered.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant