undetected-chromedriver 2.2.1

pip install undetected-chromedriver Copy PIP instructions

Released: Mar 25, 2021

selenium.webdriver.Chrome replacement with focus on stealth. not triggered by Distil / CloudFlare / Imperva / DataDome / hCaptcha and such. NOTE: results may vary due to many factors. No guarantees are given, except for ongoing efforts in understanding detection algorithms.

Navigation

Project links

Statistics

View statistics for this project via Libraries.io, or by using our public dataset on Google BigQuery

License: GNU General Public License v3 (GPLv3) (GPL-3.0)

Maintainers

Classifiers

• License
  • OSI Approved :: GNU General Public License v3 (GPLv3)
• Programming Language
  • Python :: 3
  • Python :: 3.7

Project description

undetected_chromedriver

Optimized Selenium Chromedriver patch which does not trigger anti-bot services like Distill Network / Imperva / DataDome / Botprotect.io Automatically downloads the driver binary and patches it.

• Tested from version 80 until current beta
• Patching also works on MS Edge (chromium-based) webdriver binary
• Python 3.6++

Installation

Usage

To prevent unnecessary hair-pulling and issue-raising, please mind the important note at the end of this document .

the easy way (recommended)

the V2 (beta) way

target specific chrome version

monkeypatch mode

Needs to be done before importing from selenium package

the customized way

datadome.co example

These guys have actually a powerful product, and a link to this repo, which makes me wanna test their product. Make sure you use a «clean» ip for this one.

Check both saved screenhots here

important note

Due to the inner workings of the module, it is needed to browse programmatically (ie: using .get(url) ). Never use the gui to navigate. Using your keybord and mouse for navigation causes possible detection! New Tabs: same story. If you really need multi-tabs, then open the tab with the blank page (hint: url is data:, including comma, and yes, driver accepts it) and do your thing as usual. If you follow these «rules» (actually its default behaviour), then you will have a great time for now.

chromedriver-py 90.0.4430.24

pip install chromedriver-py Copy PIP instructions

Released: Mar 15, 2021

chromedriver binaries for all platforms

Navigation

Project links

Statistics

View statistics for this project via Libraries.io, or by using our public dataset on Google BigQuery

License: Apache Software License

Tags chromedriver, cross-platform, binaries, binary

Maintainers

Classifiers

• License
  • OSI Approved :: Apache Software License
• Operating System
  • OS Independent
• Programming Language
  • Python

Project description

chromedriver-py

downloads and installs the latest chromedriver binary version for automated testing of webapps.
the installer supports linux, mac and windows operating systems.

this package is maintained by an automated update script on travis.
if a new chromedriver version is out, this package will automaticly get updated within a day.

installation

from pypi:

from github:

specific version:
choose your version here

usage

to use chromedriver just from chromedriver_py import binary_path .
you will get a string variable with the executable filepath for your operating system.

example

developer

you can trigger a custom build with a specific version in travis.
just make a new environment variable in travis settings with the name VERSION .
the key will be your desired version like 2.44 .

for the last step you have to click on settings again and hit trigger build .
this will try to get your desired version and push it to pypi.

important: don’t forget to delete the environment variable later on!

Chromedriver windows 10 64 bit

An NPM wrapper for Selenium ChromeDriver.

Building and Installing

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 Node.js), and Windows. If you spot any platform weirdness, let us know or send a patch.

By default this package, when installed, will search for an existing Chromedriver binary in your configured temp directory. If found, and it is the correct version, it will simply copy it to your node_modules directory. You can force it always download by configuring it:

Or add property into your .npmrc file.

Another option is to use PATH variable CHROMEDRIVER_FORCE_DOWNLOAD .

Custom binaries url

To use a mirror of the ChromeDriver binaries use npm config property chromedriver_cdnurl . Default is https://chromedriver.storage.googleapis.com .

Or add property into your .npmrc file.

Another option is to use PATH variable CHROMEDRIVER_CDNURL .

Custom binaries file

To get the chromedriver from the filesystem instead of a web request use the npm config property chromedriver_filepath .

Or add property into your .npmrc file.

Another option is to use the PATH variable CHROMEDRIVER_FILEPATH

This variable can be used to set either a .zip file or the binary itself, eg:

Custom download options

Install through a proxy.

Use different User-Agent.

Skipping chromedriver download

You may wish to skip the downloading of the chromedriver binary file, for example if you know for certain that it is already there or if you want to use a system binary and just use this module as an interface to interact with it.

To achieve this you can use the npm config property chromedriver_skip_download .

Or add property into your .npmrc file.

Another option is to use the PATH variable CHROMEDRIVER_SKIP_DOWNLOAD

And npm will install a link to the binary in node_modules/.bin as it is wont to do.

Running with Selenium WebDriver

(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 chromedriver binary/executable.

Below is an example of using this package via node.

You can also use the start and stop methods:

With the latest version, you can optionally receive a Promise from the chromedriver.start function:

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. You can use the package version number to install a specific version, or use the setting to a specific version. If there is a new Chromedriver version available which is not yet available as a version of node-chromedriver , the npm command npm run update-chromedriver in this repository can be used to make the required updates to this module, please submit the change as a PR. To always install the latest version of Chromedriver, use LATEST as the version number:

Or add property into your .npmrc file.

Another option is to use env variable CHROMEDRIVER_VERSION .

You can force the latest release for a specific major version by specifying LATEST_ :

You can also force a different version of chromedriver by replacing LATEST with a version number:

Detect ChromeDriver Version

The NPM package version may not be always compatible to your Chrome version. To get the chromedriver that corresponds to the version of Chrome installed, you can use the npm config property detect_chromedriver_version .

Or add property into your .npmrc file.

Another option is to use environment variable DETECT_CHROMEDRIVER_VERSION .

Note: When the property detect_chromedriver_version is provided, chromedriver_version and chromedriver_filepath properties are ignored.

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.

Supported Node.js versions

We will do our best to support every supported Node.js versions. See nodejs/Release for the current supported versions. You can also view our build scripts and check the versions there.

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.

We have added VS Code Remote support with containers. If you are on Windows, set git config core.autocrlf input so you don’t get git errors.

Thanks for Obvious and their PhantomJS project for heavy inspiration! Check their project on Github.

Licensed under the Apache License, Version 2.0.

Which ChromeDriver version is compatible with which Chrome Browser version?

Actually I’m a bit confused. Although I read several resources about this.

For having a test of Selenium 3 using ChromeBrowser we need an extra app called ChromeDriver.

I found this text from GitHub:

ChromeDriver is only compatible with Chrome version 12.0.712.0 or newer. If you need to test an older version of Chrome, use Selenium RC and a Selenium-backed WebDriver instance.

My question is are all ChromeDriver versions compatible with all Chrome version? No conflict between each version?

Where can I find documentation of all versions matching between the ChromeDriver & ChromeBrowser?

7 Answers 7

I found, that chrome and chromedriver versions support policy has changed recently.

• If you are using Chrome version 90, please download ChromeDriver 90.0.4430.24
• If you are using Chrome version 89, please download ChromeDriver 89.0.4389.23
• If you are using Chrome version 88, please download ChromeDriver 88.0.4324.96
• If you are using Chrome version 87, please download ChromeDriver 87.0.4280.88
• If you are using Chrome version 86, please download ChromeDriver 86.0.4240.22
• If you are using Chrome version 85, please download ChromeDriver 85.0.4183.87
• If you are using Chrome version 84, please download ChromeDriver 84.0.4147.30
• If you are using Chrome version 83, please download ChromeDriver 83.0.4103.39
• If you are using Chrome version 81, please download ChromeDriver 81.0.4044.69
• If you are using Chrome version 80, please download ChromeDriver 80.0.3987.106
• If you are using Chrome version 79, please download ChromeDriver 79.0.3945.36
• If you are using Chrome version 78, please download ChromeDriver 78.0.3904.105
• If you are using Chrome version 77, please download ChromeDriver 77.0.3865.40
• If you are using Chrome version 76, please download ChromeDriver 76.0.3809.126
• If you are using Chrome version 75, please download ChromeDriver 75.0.3770.140
• If you are using Chrome version 74, please download ChromeDriver 74.0.3729.6
• If you are using Chrome version 73, please download ChromeDriver 73.0.3683.68
• For older version of Chrome, please see Barett’s anwer

There is general guide to select version of crhomedriver for specific chrome version: https://sites.google.com/a/chromium.org/chromedriver/downloads/version-selection

Here is excerpt:

• First, find out which version of Chrome you are using. Let’s say you have Chrome 72.0.3626.81.
• Take the Chrome version number, remove the last part, and append the result to URL «https://chromedriver.storage.googleapis.com/LATEST_RELEASE_». For example, with Chrome version 72.0.3626.81, you’d get a URL «https://chromedriver.storage.googleapis.com/LATEST_RELEASE_72.0.3626».
• Use the URL created in the last step to retrieve a small file containing the version of ChromeDriver to use. For example, the above URL will get your a file containing «72.0.3626.69». (The actual number may change in the future, of course.)
• Use the version number retrieved from the previous step to construct the URL to download ChromeDriver. With version 72.0.3626.69, the URL would be «https://chromedriver.storage.googleapis.com/index.html?path=72.0.3626.69/».
• After the initial download, it is recommended that you occasionally go through the above process again to see if there are any bug fix releases.

Note, that this version selection algorithm can be easily automated. For example, simple powershell script in another answer has automated chromedriver updating on windows platform.

Chromedriver windows 10 64 bit

This file contains high-level info about how ChromeDriver works and how to contribute. If you are looking for information on how to use ChromeDriver, please see the ChromeDriver user site.

ChromeDriver is an implementation of the WebDriver standard, which allows users to automate testing of their website across browsers.

ChromeDriver source code is located in the Chromium source repository, and shares the same build tools as Chromium. To build ChromeDriver, please first follow the instructions to download and build Chromium.

Once you have set up the build environment, build ChromeDriver by building the chromedriver target, e.g.,

This will create an executable binary in the build folder named chromedriver[.exe] .

Once built, ChromeDriver can be used with various third-party libraries that support WebDriver protocol, including language bindings provided by Selenium.

Note that if your build target OS is Android (i.e., you have target_os = «android» in your args.gn file), you will need to use the following command to build ChromeDriver targeting the host system:

Verifying the Build

For testing purposes, ChromeDriver can be used interactively with python. The following is an example on Linux. It assumes that you downloaded Chromium repository at

/chromium/src, and you used out/Default as the build location. You may need to adjust the paths if you used different locations. The following code uses our own testing API, not the commonly used Python binding provided by Selenium.

By default, ChromeDriver will look in its own directory for Chrome to use. If Chrome is not found there, it will use the system installed Chrome.

To use ChromeDriver with Chrome on Android pass the Android package name in the chromeOptions.androidPackage capability when creating the driver. You also need to have Android SDK’s Android Debug Bridge (adb) server running. For more detailed instructions see the user site.

ChromeDriver is shipped separately from Chrome. It controls Chrome out of process through DevTools. ChromeDriver is a standalone server which communicates with the WebDriver client via the WebDriver wire protocol, which is essentially synchronous JSON commands over HTTP. WebDriver clients are available in many languages, and many are available from the open source Selenium WebDriver project. ChromeDriver uses the webserver from net/server.

Additional information is available on the following pages:

• Threading: ChromeDriver threading model.
• Chrome Connection: How ChromeDriver connects to Chrome and controls it.
• DevTools Event Listener: How ChromeDriver responds to events from Chrome DevTools.
• Run JavaScript Code: How ChromeDriver sends JavaScript code to Chrome for execution.

Code structure (relative to this file)

(this directory): Implements chromedriver commands.

chrome/: A basic interface for controlling Chrome. Should not depend on or reference WebDriver-related code or concepts.

js/: Javascript helper scripts.

net/: Code to deal with network communication, such as connection to DevTools.

client/: Code for a python client.

server/: Code for the chromedriver server. A python wrapper to the chromedriver server.

There are several test suites for verifying ChromeDriver’s correctness. For details, see the testing page.

Find an open issue and submit a patch for review by an individual listed in the OWNERS file in this directory. Issues are tracked in ChromeDriver issue tracker.