chrome-launcher
chrome-launcher copied to clipboard
GoogleChrome
Launch Google Chrome with ease from node.
In [Build #70](https://travis-ci.org/maple3142/Blog/builds/353838783), I get a error message: ``` Launch Error: { Error: connect ECONNREFUSED 127.0.0.1:41697 at Object._errnoException (util.js:1022:11) at _exceptionWithHostPort (util.js:1044:20) at TCPConnectWrap.afterConnect [as oncomplete] (net.js:1198:14) [stack]: 'Error: connect...
Reported by @jayflux ``` CHROME_PATH=/usr/bin/google-chrome NODE_EXTRA_CA_CERTS=/etc/pki/tls/certs/ca-bundle.crt _=/usr/bin/env [developer@sounds-performance sounds-performance]$ sudo -E node index.js which: no chromium-browser in (/sbin:/bin:/usr/sbin:/usr/bin) which: no chromium in (/sbin:/bin:/usr/sbin:/usr/bin) { Error: connect ECONNREFUSED 127.0.0.1:33429 at Object._errnoException...
Не работает массовое копировать/вырезать и прочее , что раньше работало с другой оболочкой.
A test for https://github.com/GoogleChrome/chrome-launcher/issues/81  see also https://github.com/GoogleChrome/lighthouse/pull/4192#issuecomment-356150346 > i was thinking a more functional test. e.g. some module that require()s chrome-launcher successfully typechecks with TS.
I have this: ```js chromeLauncher.launch({ enableExtensions: true, startingUrl: 'chrome-extension://idbanmbeeadlaanhdemgngeooobbadde/dist/index.html' }) .then(chrome => { console.log(`Chrome debugging port running on ${chrome.port}`); }); ``` I get this:  any idea...
I'm setting handleSIGINT: false When i press ctrl + c chrome closes, which it shouldn't Running on OSX High Sierra, Chrome 63.0.3239.108
if some flag is set to a empty string chrome launcher doesnt add the error in staring chrome in the stack strace . Have included the sample code here since...
`--test-type=foo` has some interesting effects: https://cs.chromium.org/search/?q=kTestType%5Cb&type=cs Need to collect its effects and make sure ALL users of chrome-launcher want these changes made.
- I have created a chrome instance at a port(9222) - My application makes multiple simultaneous connections with the chrome instance.(close to 150 at a time). - I'm running into...
_From @guilhermevrs on July 19, 2017 9:32_ **Initial URL:** https://developers.google.com/web/tools/lighthouse/ **Chrome Version:** 61.0.3160.0 When lauching `./node_modules/.bin/lighthouse https://developers.google.com/web/tools/lighthouse/` I get the following: ``` ChromeLauncher Waiting for browser. +0ms ChromeLauncher Waiting for...
