feat: add appium:showChromedriverLog support (#66)

* feat: add appium:showChromedriverLog support

* tweak tyoe

Author: KazuCocoa

README.md

@@ -39,6 +39,7 @@ package in your `package.json`)
 |`appium:appId`|[Required] The app package ID, if you want Appium to use an app already on the TV. Exclusive with `appium:app`|
 |`appium:app`|[Optional] An absolute path to your `.ipk` app file, if you want Appium to install the app.|
 |`appium:debuggerPort`|[Optional; default `9998`] The port on the device exposed for remote Chromium debugging.|
+| `appium:showChromedriverLog` 	  | If set to `true` then all the output from chromedriver binary will be forwarded to the Appium server log. `false` by default. |
 |`appium:chromedriverExecutable`(*)|[Optional] Most LG TVs run a very old version of Chrome. Because this driver uses Chromedriver under the hood, you'll need to have a very old version of Chromedriver handy that works with the version of Chrome backing the apps on your TV. In our testing, we've found Chromedriver 2.36 to work with most TVs. You need to tell the driver where you've installed this version of Chromedriver using the `appium:chromedriverExecutable` capability, passing in an absolute path to the Chromedriver binary.|
 | `appium:chromedriverExecutableDir`(*) | [Optional] Full path to the folder where chromedriver executables are located. This folder is used then to store the downloaded chromedriver executables if automatic download is enabled with `chromedriver_autodownload` security flag. Please read [Automatic Discovery of Compatible Chromedriver in appium-uiautomator2-driver](https://github.com/appium/appium-uiautomator2-driver?tab=readme-ov-file#automatic-discovery-of-compatible-chromedriver) for more details. If the chrome version on the TV is lower than v63 major version, the using chrome version will be `Chrome/63.0.3239.0` forcefully to use chromedriver 2.36 for the session. Lower chromedriver could raise `cannot find Chrome binary` error, which prevent starting chromedriver session. |
 |`appium:websocketPort`|[Optional; default `3000`] The websocket port on the device exposed for remote control|

lib/constraints.js

@@ -57,6 +57,9 @@ export const CAP_CONSTRAINTS = Object.freeze(
     keyCooldown: {
       isNumber: true,
     },
+    showChromedriverLog: {
+      isBoolean: true
+    },
   })
 );
 

lib/driver.js

@@ -123,6 +123,7 @@ export class WebOSDriver extends BaseDriver {
       fullReset,
       deviceHost,
       debuggerPort,
+      showChromedriverLog,
       chromedriverExecutable,
       chromedriverExecutableDir,
       appLaunchCooldown,
@@ -201,6 +202,7 @@ export class WebOSDriver extends BaseDriver {
       executable: /** @type {string} */ (chromedriverExecutable),
       executableDir: /** @type {string} */ (chromedriverExecutableDir),
       isAutodownloadEnabled: /** @type {Boolean} */ (this.#isChromedriverAutodownloadEnabled()),
+      verbose: /** @type {Boolean | undefined} */ (showChromedriverLog),
     });
 
     log.info('Waiting for app launch to take effect');
@@ -298,7 +300,7 @@ export class WebOSDriver extends BaseDriver {
   /**
    * @param {StartChromedriverOptions} opts
    */
-  async startChromedriver({debuggerHost, debuggerPort, executable, executableDir, isAutodownloadEnabled}) {
+  async startChromedriver({debuggerHost, debuggerPort, executable, executableDir, isAutodownloadEnabled, verbose}) {
     const debuggerAddress = `${debuggerHost}:${debuggerPort}`;
 
 
@@ -332,7 +334,8 @@ export class WebOSDriver extends BaseDriver {
       executableDir,
       isAutodownloadEnabled,
       // @ts-ignore
-      details: {info: result}
+      details: {info: result},
+      verbose
     });
 
     // XXX: goog:chromeOptions in newer versions, chromeOptions in older

lib/types.ts

@@ -53,6 +53,7 @@ export interface StartChromedriverOptions {
   executable?: string;
   executableDir?: string;
   isAutodownloadEnabled: boolean;
+  verbose?: boolean;
 }
 
 /**