npmpackage.info

Gathering detailed insights and metrics for karma-chrome-launcher

Other packages similar to karma-chrome-launcher

@types/karma-chrome-launcher

3.1.4

TypeScript definitions for karma-chrome-launcher

chrome-launcher

1.1.2

Launch latest Chrome with the Devtools Protocol port open

karma-firefox-launcher

2.1.3

A Karma plugin. Launcher for Firefox.

@chiragrupani/karma-chromium-edge-launcher

2.4.1

A Karma plugin. Launcher for different Chromium Edge channels - Dev, Canary, Beta and Stable

Gathering detailed insights and metrics for karma-chrome-launcher

karma-chrome-launcher

A Karma plugin. Launcher for Chrome and Chrome Canary.

3.2.0

469

MIT

JavaScript

663,792,095 3.4

Installations

npm install karma-chrome-launcher

Pull Requests

Open

23

Total

123

Closed

49

Merged

51

Issues

Open

59

Total

164

Closed

105

Releases

v3.2.0

Published on 20 Apr 2023

v3.1.1

Published on 09 Mar 2022

v3.1.0

Published on 13 Aug 2019

v3.0.0

Published on 12 Jul 2019

v2.2.0

Published on 23 Jun 2017

v2.1.1

Published on 05 May 2017

View all 26 releases

Developer

karma-runner

Developer Guide

BETA

Module System

CommonJS

Min. Node Version

Typescript Support

No

Node Version

18.16.0

NPM Version

7.24.2 Statistics

469 Stars

198 Commits

119 Forks

15 Watching

16 Branches

49 Contributors

Updated on 22 Nov 2024

Languages

JavaScript (100%)

Total Downloads

Cumulative downloads

Total Downloads

663,792,095

Last day

-1.5%

506,528

Compared to previous day

Last week

3.9%

2,689,526

Compared to previous week

Last month

8.9%

10,966,888

Compared to previous month

Last year

1.9%

119,817,688

Compared to previous year

Daily Downloads

Weekly Downloads

Monthly Downloads

Yearly Downloads

Dependencies

which

Dev Dependencies

chai karma mocha sinon standard karma-mocha @commitlint/cli semantic-release @semantic-release/git @commitlint/config-angular @semantic-release/changelog

Versions

karma-chrome-launcher

Launcher for Google Chrome, Google Chrome Canary and Google Chromium.

Installation

The easiest way is to keep karma-chrome-launcher as a devDependency in your package.json, by running

1$ npm i -D karma-chrome-launcher

Configuration

1// karma.conf.js
2module.exports = function(config) {
3  config.set({
4    browsers: ['Chrome', 'Chrome_without_security'], // You may use 'ChromeCanary', 'Chromium' or any other supported browser
5
6    // you can define custom flags
7    customLaunchers: {
8      Chrome_without_security: {
9        base: 'Chrome',
10        flags: ['--disable-web-security', '--disable-site-isolation-trials']
11      }
12    }
13  })
14}

The --user-data-dir is set to a temporary directory but can be overridden on a custom launcher as shown below. One reason to do this is to have a permanent Chrome user data directory inside the project directory to be able to install plugins there (e.g. JetBrains IDE Support plugin).

1customLaunchers: {
2  Chrome_with_debugging: {
3    base: 'Chrome',
4    chromeDataDir: path.resolve(__dirname, '.chrome')
5  }
6}

You can pass list of browsers as a CLI argument too:

1$ karma start --browsers Chrome,Chrome_without_security

Headless Chromium with Puppeteer

The Chrome DevTools team created Puppeteer - it will automatically install Chromium for all platforms and contains everything you need to run it from within your CI.

Available Browsers

Note: Headless mode requires a browser version >= 59

Chrome (CHROME_BIN)
ChromeHeadless (CHROME_BIN)
Chromium (CHROMIUM_BIN)
ChromiumHeadless (CHROMIUM_BIN)
ChromeCanary (CHROME_CANARY_BIN)
ChromeCanaryHeadless (CHROME_CANARY_BIN)
Dartium (DARTIUM_BIN)

Usage

1$ npm i -D puppeteer karma-chrome-launcher

1// karma.conf.js
2process.env.CHROME_BIN = require('puppeteer').executablePath()
3
4module.exports = function(config) {
5  config.set({
6    browsers: ['ChromeHeadless']
7  })
8}

For more information on Karma see the homepage.

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.

4

Code-Review

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

3

Pinned-Dependencies

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

0

Token-Permissions

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

0

Maintained

Determines if the project is "actively maintained".

0

CII-Best-Practices

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

0

Fuzzing

Determines if the project uses fuzzing.

0

Security-Policy

Determines if the project has published a security policy.

0

SAST

Determines if the project uses static code analysis.

0

Vulnerabilities

Determines if the project has open, known unfixed vulnerabilities.

Score

3.4

/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.

Learn More