ChromeDriver for Selenium
An NPM wrapper for Selenium ChromeDriver.
npm install chromedriver
Or grab the source and
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.
To use a mirror of the ChromeDriver binaries use npm config property
npm install chromedriver --chromedriver_cdnurl=http://npm.taobao.org/mirrors/chromedriver
Or add property into your
Another option is to use PATH variable
CHROMEDRIVER_CDNURL=http://npm.taobao.org/mirrors/chromedriver npm install chromedriver
And npm will install a link to the binary in
it is wont to do.
;var webdriver = ;var driver =;
(Tested for selenium-webdriver version
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.
The package exports a
path string that contains the path to the
Below is an example of using this package via node.
var childProcess = ;var chromedriver = ;var binPath = chromedriverpath;var childArgs ='some argument';childProcess;
You can also use the start and stop methods:
var chromedriver = ;args =// optional arguments;chromedriverstartargs;// run your testschromedriver;
Note: if your tests are ran asynchronously, chromedriver.stop() will have to be executed as a callback at the end of your tests
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.
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.
Questions, comments, bug reports, and pull requests are all welcome. Submit them at the project on GitHub.
Bug reports that include steps-to-reproduce (including code) are the best. Even better, make them in the form of pull requests.
Thanks for Obvious and their PhantomJS project for heavy inspiration! Check their project on Github.
Licensed under the Apache License, Version 2.0.