Closed crfrolik closed 3 years ago
Not sure if this is relevant; it could be, since it would only impact new Chrome installations: https://www.ghacks.net/2020/06/11/google-chrome-is-soon-going-to-be-installed-in-a-different-directory-on-windows/
Can you please tell us:
Under the covers, we use chrome-launcher@0.13.4
, which appears to be compatible with the new chrome.exe location mentioned in the article.
While we are troubleshooting the issue, you may use the env.runner
configuration property to provide an absolute path to your version of Chrome:
Wallaby.js Configuration Example
module.exports = () => ({
autoDetect: true,
env: {
kind: 'chrome',
runner: 'C:\\Program Files (x86)\\Google\\Chrome\\Application\\chrome.exe'
}
});
Looks like it is present here: C:\Program Files\Google\Chrome\Application\chrome.exe
I installed it from here: https://www.google.com/chrome/index.html
Thanks for mentioning that you use chrome-launcher
; I was able to discover that they will use the CHROME_PATH
environment variable if it is set. Setting this resolved my issue.
Issue description or question
Installed wallaby into WebStorm on a new computer (Windows 10). The computer does have nodejs v14 installed and Chrome v91.
However, when I start it I get this error:
Wallaby diagnostics report