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