Current Dev State

static/js/ketcher2/node_modules/chromedriver/README.md

@@ -0,0 +1,187 @@
+ChromeDriver
+=======
+[![Build status](https://travis-ci.org/giggio/node-chromedriver.svg)](https://travis-ci.org/giggio/node-chromedriver/) [![Build status](https://ci.appveyor.com/api/projects/status/wr4c16rs5q113vy3?svg=true)](https://ci.appveyor.com/project/giggio/node-chromedriver)
+[![npm](https://img.shields.io/npm/dt/chromedriver.svg)](https://www.npmjs.com/package/chromedriver)
+
+An NPM wrapper for Selenium [ChromeDriver](https://sites.google.com/a/chromium.org/chromedriver/).
+
+Building and Installing
+-----------------------
+
+```shell
+npm install chromedriver
+```
+
+Or grab the source and
+
+```shell
+node ./install.js
+```
+
+What this is really doing is just grabbing a particular "blessed" (by
+this module) version of ChromeDriver. As new versions are released
+and vetted, this module will be updated accordingly.
+
+The package has been set up to fetch and run ChromeDriver for MacOS (darwin),
+Linux based platforms (as identified by nodejs), and Windows.  If you
+spot any platform weirdnesses, let us know or send a patch.
+
+### Custom binaries url
+
+To use a mirror of the ChromeDriver binaries use npm config property `chromedriver_cdnurl`.
+Default is `http://chromedriver.storage.googleapis.com`.
+
+```shell
+npm install chromedriver --chromedriver_cdnurl=https://npm.taobao.org/mirrors/chromedriver
+```
+
+Or add property into your [`.npmrc`](https://docs.npmjs.com/files/npmrc) file.
+
+```
+chromedriver_cdnurl=https://npm.taobao.org/mirrors/chromedriver
+```
+
+Another option is to use PATH variable `CHROMEDRIVER_CDNURL`.
+
+```shell
+CHROMEDRIVER_CDNURL=https://npm.taobao.org/mirrors/chromedriver npm install chromedriver
+```
+
+### Custom binaries file
+
+To get the chromedriver from the filesystem instead of a web request use the npm config property `chromedriver_filepath`.
+
+```shell
+npm install chromedriver --chromedriver_filepath=/path/to/chromedriver_mac64.zip
+```
+
+Or add property into your [`.npmrc`](https://docs.npmjs.com/files/npmrc) file.
+
+```
+chromedriver_filepath=/path/to/chromedriver_mac64.zip
+```
+
+Another option is to use the PATH variable `CHROMEDRIVER_FILEPATH`
+
+```shell
+CHROMEDRIVER_FILEPATH=/path/to/chromedriver_mac64.zip
+```
+
+Running
+-------
+
+```shell
+bin/chromedriver [arguments]
+```
+
+And npm will install a link to the binary in `node_modules/.bin` as
+it is wont to do.
+
+Running with Selenium WebDriver
+-------------------------------
+
+```javascript
+require('chromedriver');
+var webdriver = require('selenium-webdriver');
+var driver = new webdriver.Builder()
+  .forBrowser('chrome')
+  .build();
+```
+
+(Tested for selenium-webdriver version `2.48.2`)
+
+The path will be added to the process automatically, you don't need to configure it.
+But you can get it from `require('chromedriver').path` if you want it.
+
+Running via node
+----------------
+
+The package exports a `path` string that contains the path to the
+chromdriver binary/executable.
+
+Below is an example of using this package via node.
+
+```javascript
+var childProcess = require('child_process');
+var chromedriver = require('chromedriver');
+var binPath = chromedriver.path;
+
+var childArgs = [
+  'some argument'
+];
+
+childProcess.execFile(binPath, childArgs, function(err, stdout, stderr) {
+  // handle results
+});
+
+```
+
+You can also use the start and stop methods:
+
+```javascript
+var chromedriver = require('chromedriver');
+
+args = [
+	// optional arguments
+];
+chromedriver.start(args);
+// run your tests
+chromedriver.stop();
+
+```
+Note: if your tests are ran asynchronously, chromedriver.stop() will have to be
+executed as a callback at the end of your tests
+
+Versioning
+----------
+
+The NPM package version tracks the version of chromedriver that will be installed,
+with an additional build number that is used for revisions to the installer.
+You can use the package version number to install a specific version, or use the
+setting to a specific version. To always install the latest version of Chromedriver,
+use `LATEST` as the version number:
+
+```shell
+npm install chromedriver --chromedriver_version=LATEST
+```
+
+Or add property into your [`.npmrc`](https://docs.npmjs.com/files/npmrc) file.
+
+```
+chromedriver_version=LATEST
+```
+
+Another option is to use env variable `CHROMEDRIVER_VERSION`.
+
+```shell
+CHROMEDRIVER_VERSION=LATEST npm install chromedriver
+```
+
+A Note on chromedriver
+-------------------
+
+Chromedriver is not a library for NodeJS.
+
+This is an _NPM wrapper_ and can be used to conveniently make ChromeDriver available
+It is not a Node JS wrapper.
+
+Contributing
+------------
+
+Questions, comments, bug reports, and pull requests are all welcome.  Submit them at
+[the project on GitHub](https://github.com/giggio/node-chromedriver/).
+
+Bug reports that include steps-to-reproduce (including code) are the
+best. Even better, make them in the form of pull requests.
+
+Author
+------
+
+[Giovanni Bassi](https://github.com/giggio)
+
+Thanks for Obvious and their PhantomJS project for heavy inspiration! Check their project on [Github](https://github.com/Obvious/phantomjs/tree/master/bin).
+
+License
+-------
+
+Licensed under the Apache License, Version 2.0.