We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
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?
The text was updated successfully, but these errors were encountered:
fix: allow overriding of default debug port
1284e5b
This allows the --remote-debugging-port flag to be overridden with a custom port when using chrome headless. Fixes #187
6015ece
ebb82c9
feat: allow overriding of the default debug port
26ae9f4
No branches or pull requests
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:
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:
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?
The text was updated successfully, but these errors were encountered: