Same on my Windows 7. karma-chrome-launcher 0.1.12.
Version 0.1.8 works on the same PC.

I have done some debugging and the problem is the version of Node.js.
Basically fs.accessSync is not supported, the code swallows the exception and exhausts all the possible paths.

function getChromeExe(chromeDirName) {
  ...
  for (i = 0; i < prefixes.length; i++) {
    prefix = prefixes[i];
    try {
      windowsChromeDirectory = path.join(prefix, suffix);
      fs.accessSync(windowsChromeDirectory);
      return windowsChromeDirectory;
    } catch (e) {
      console.log('%s - %s', windowsChromeDirectory, e);  //<---- added by me
    }
  }

  return windowsChromeDirectory;
}

Generates

C:\Users\vm\AppData\Local\Google\Chrome\Application\chrome.exe - TypeError: Object #<Object> has no method 'accessSync'
C:\Program Files\Google\Chrome\Application\chrome.exe - TypeError: Object #<Object> has no method 'accessSync'
C:\Program Files (x86)\Google\Chrome\Application\chrome.exe - TypeError: Object #<Object> has no method 'accessSync'
C:\Users\vm\AppData\Local\Google\Chrome SxS\Application\chrome.exe - TypeError: Object #<Object> has no method 'accessSync'
C:\Program Files\Google\Chrome SxS\Application\chrome.exe - TypeError: Object #<Object> has no method 'accessSync'
C:\Program Files (x86)\Google\Chrome SxS\Application\chrome.exe - TypeError: Object #<Object> has no method 'accessSync'

Cannot find chrome.app in OSX #53

Description

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions