-
Notifications
You must be signed in to change notification settings - Fork 48
Error: Could not start chrome: Error: spawn google-chrome-unstable ENOENT #5
Comments
By default NickJS tries to launch the google-chrome-unstable binary which is not in your PATH. You can specify where it is with the CHROME_PATH environment variable, for example: Does that work? |
I know that from the error message, but on Windows, you don't have google-chrome-unstable |
On Windows you can set environment variables too, as explained here: https://superuser.com/questions/79612/setting-and-getting-windows-environment-variables-from-the-command-prompt You have to set CHROME_PATH to the exact path of you Google Chrome executable (chrome.exe) |
OK, so NickJS read from CHROME_PATH by default. You should take the executionpath as param for instantiate NickJS, or spawn the Chrome process in the same way as Chromeless/Puppeteer does. |
CHROME_PATH is not set by default, on any OS. You have to set it yourself. It's true that NickJS' launch could be improved in many ways. We'll continue improving it. In the meatime, PRs welcome :) |
I seem to not be able to get it to open Chrome either.
I just have this line at the top of my app.js
|
Can you try by declaring your environment variable in your shell or in the windows env? |
Is there an actual fix for this that works ? |
Hi @laamb, there is. You have to make sure the CHROME_PATH environment variable contains the path to your Google Chrome executable. |
With Node 6.11.3 LTS and Node 8.5.0
Chrome Version 61.0.3163.91 (Official Build) (64-bit)
Using sample on https://nickjs.org/
It always say: "Error: Could not start chrome: Error: spawn google-chrome-unstable ENOENT"
Same environment, I run puppeteer normally
Result is HeadlessChrome/62.0.3198.0
The text was updated successfully, but these errors were encountered: