npmpackage.info

Gathering detailed insights and metrics for wdio-chromedriver-service

Gathering detailed insights and metrics for wdio-chromedriver-service

wdio-chromedriver-service

WebdriverIO service to start & stop ChromeDriver

8.1.1

36

MIT

TypeScript

Installations

npm install wdio-chromedriver-service

Score

51.7

Supply Chain

87.5

Quality

74.5

Maintenance

50

Vulnerability

96.1

License

Pull Requests

Open

2

Total

318

Closed

61

Merged

255

Issues

Open

2

Total

41

Closed

39

Releases

20

Release 8.1.1

Published on 14 Feb 2023

Release 8.1.0

Published on 13 Feb 2023

Release 8.0.1

Published on 05 Dec 2022

Release 8.0.0

Published on 30 Sept 2022

Release 8.0.0-alpha.1

Published on 16 Aug 2022

Release 8.0.0-alpha.0

Published on 16 Aug 2022

View all 20 releases

Developer

webdriverio-community

Developer Guide

BETA

Module System

ESM

Min. Node Version

^16.13 || >=18

Typescript Support

Yes

Node Version

18.14.0

NPM Version

9.3.1

Statistics

36 Stars

347 Commits

26 Forks

10 Watching

4 Branches

22 Contributors

Updated on 01 May 2024

Languages

TypeScript (98.49%)

JavaScript (1.51%)

Total Downloads

Cumulative downloads

Total Downloads

43,401,311

Last day

2%

32,507

Compared to previous day

Last week

9.6%

201,657

Compared to previous week

Last month

-0.4%

777,660

Compared to previous month

Last year

-6%

9,868,769

Compared to previous year

Daily Downloads

Weekly Downloads

Monthly Downloads

Yearly Downloads

Versions

⚠️ DEPRECATION WARNING: This service got deprecated and is no longer maintained. If you use WebdriverIO v8.14 or higher. We recommend to remove the service as dependency and from your WebdriverIO configuration as it is no longer needed. For more information, please read this blog post.

WDIO ChromeDriver Service

This service helps you to run ChromeDriver seamlessly when running tests with the WDIO testrunner. It uses the chromedriver NPM package that wraps ChromeDriver for you.

Note: this service does not require a Selenium server, but uses ChromeDriver to communicate with the browser directly.

Obviously, it only supports:

1capabilities: [{
2    browserName: 'chrome'
3}]

Installation

The easiest way is to keep wdio-chromedriver-service as a devDependency in your package.json.

1{
2  "devDependencies": {
3    "wdio-chromedriver-service": "^8.0.0"
4  }
5}

You can do it by:

1npm install wdio-chromedriver-service --save-dev

Note: You have to install chromedriver separately, as it's a peerDependency of this project, and you're free to choose which version to use. Depending of which version of Chrome you have installed on your system you should install the same version of chromedriver. Install it using:

1npm install chromedriver --save-dev
2# if you have Chrome 104 installed on your machine do
3npm install chromedriver@104 --save-dev

Instructions on how to install WebdriverIO can be found here.

Configuration

By design, only Google Chrome is available (when installed on the host system). In order to use the service you need to add chromedriver to your service array:

1// wdio.conf.js
2export.config = {
3  outputDir: 'all-logs',
4  // ...
5  services: [
6    ['chromedriver', {
7        logFileName: 'wdio-chromedriver.log', // default
8        outputDir: 'driver-logs', // overwrites the config.outputDir
9        args: ['--silent']
10    }]
11  ],
12  // ...
13};

Options

port

The port on which the driver should run on

Example: 9515

Type: number

path

The path on which the driver should run on

Example: /

Type: string

protocol

The protocol on which the driver should use

Example: http

Type: string

hostname

The protocol on which the driver should use

Example: localhost

Type: string

pollTimeout

The startup timeout in ms, it checks if the port is open before starting ChromeDriver and then checks again if the it is closed after starting it.

Example: 10000

Type: number

outputDir

The path where the output of the ChromeDriver server should be stored (uses the config.outputDir by default when not set).

Example: driver-logs

Type: string

logFileName

The name of the log file to be written in outputDir.

Example: wdio-chromedriver.log

Type: string

chromedriverCustomPath

To use a custom chromedriver different than the one installed through the "chromedriver npm module", provide the path.

Example: /path/to/chromedriver (Linux / MacOS), ./chromedriver.exe or d:/driver/chromedriver.exe (Windows)

Type: string

For more information on WebdriverIO see the homepage.

Empty State

No vulnerabilities found.

10

Dangerous-Workflow

Determines if the project's GitHub Action workflows avoid dangerous patterns.

10

Binary-Artifacts

Determines if the project has generated executable (binary) artifacts in the source repository.

10

License

Determines if the project has defined a license.

3

Pinned-Dependencies

Determines if the project has declared and pinned the dependencies of its build process.

0

Code-Review

Determines if the project requires human code review before pull requests (aka merge requests) are merged.

0

Maintained

Determines if the project is "actively maintained".

0

Token-Permissions

Determines if the project's workflows follow the principle of least privilege.

0

CII-Best-Practices

Determines if the project has an OpenSSF (formerly CII) Best Practices Badge.

0

Security-Policy

Determines if the project has published a security policy.

0

Fuzzing

Determines if the project uses fuzzing.

0

Branch-Protection

Determines if the default and release branches are protected with GitHub's branch protection settings.

0

SAST

Determines if the project uses static code analysis.

0

Vulnerabilities

Determines if the project has open, known unfixed vulnerabilities.

Score

2.7

/10

Last Scanned on 2024-11-18

The Open Source Security Foundation is a cross-industry collaboration to improve the security of open source software (OSS). The Scorecard provides security health metrics for open source projects.