chrome-launcher
chrome-launcher copied to clipboard
GoogleChrome
Launch Google Chrome with ease from node.
This is how it works today: Manually provided chrome location: - CHROME_PATH / LIGHTHOUSE_CHROMIUM_PATH - (mac) Any Chrome you've ever opened (uses `lsregister`) Note: this finds _lots_ of installations! https://gist.github.com/connorjclark/97fef0c9a209b4bd09c87f4125a9b678...
I've added new option `waitForInspectableTarget` that allows to wait until target list is available. It should fix #145.
I'm trying to integrate the chrome logs created when the logLevel flag is set to verbose into my logging framework, but am having trouble. I initially tried capturing the stdout...
#### Environment Information System: Windows 10 Node.js version: v14.18.1 Chrome version: 96.0.4664.55 #### Provide the steps to reproduce When I use custom userDataDir, and remove it after chrome exit. ```...
Hello, could you please provide some clarity on what this error might mean and why we can't kill a Chrome instance that we've previously launched using `chrome-launcher`? This happens on...
I have a react application with multiple tabs, in each tab we can add one or multiple highcharts. Once we reach the third tab, the application becomes very slow, took...
In WSL2, chrome-launcher running on Linux starts the Chrome instance installed on Windows, even if Chrome is also installed on Linux. IMO the precedence should be changed to prioritize the...
I suggest removing this code, the flag is no longer used in chrome. ``` if (process.platform === 'linux') { flags.push('--disable-setuid-sandbox'); } ```
_From @paulirish on June 20, 2017 21:59_ This is a bit of carryover from #2544. It was failing 100% of the time and now its more like 5%. Example build:...
