Skip to content

Can't override default remote-debugging-port using ChromeHeadless #187

@yevit

Description

@yevit

I'm unable to set the remote debugging port when using ChromeHeadless, it always sticks to the default port 9222.

I'm using the following karma config:

...
customLaunchers: {
     ChromeHeadlessDebugging: {
          base: 'ChromeHeadless',
          flags: [
                 '--remote-debugging-port=9333'
          ]
     }
}

When this is used the argument for port 9333 is ignored and 9222 is used.

I've done a bit of investigation and believe that it is due to the way the arguments are concatenated on or around this line https://github.com/karma-runner/karma-chrome-launcher/blob/master/index.js#L168. This makes the aruments array look like this:

[ '--user-data-dir=C:\\Users\\####\\AppData\\Local\\Temp\\karma-84831659',
  '--no-default-browser-check',
  '--no-first-run',
  '--disable-default-apps',
  '--disable-popup-blocking',
  '--disable-translate',
  '--disable-background-timer-throttling',
  '--disable-renderer-backgrounding',
  '--disable-device-discovery-notifications',
  '--remote-debugging-port=9333',
  'http://localhost:9876/?id=84831659',
  '--headless',
  '--disable-gpu',
  '--remote-debugging-port=9222' ]

I'm guessing the issue is because of ordering of the arguments in the array and the ones in the karma config should be at the bottom?

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions