Alexandro.Net

Version 1.0.2

@stackline/karma-chrome-launcher

A Karma plugin. Launcher for Chrome and Chrome Canary.

Independent maintenance of karma-chrome-launcher 3.2.0. Original authors and licenses are retained.

Installation

# Preserve existing imports with an npm alias
npm install karma-chrome-launcher@npm:@stackline/karma-chrome-launcher@1.0.2
# Or use the scoped package name in your imports
npm install @stackline/karma-chrome-launcher@1.0.2

Node.js: See compatibility notes. Read the compatibility and maintenance notes before migrating.

Usage and API

@stackline/karma-chrome-launcher

A Karma plugin. Launcher for Chrome and Chrome Canary.

npm version license GitHub repository Docs Reddit community

Documentation | npm | Issues | Repository

Current package version: 1.0.2

Why this package?

@stackline/karma-chrome-launcher is the Stackline-maintained distribution of karma-chrome-launcher@3.2.0. It is an independent continuation of karma-chrome-launcher; original authors and licenses remain credited below.

Compatibility

Item Value
Package @stackline/karma-chrome-launcher@1.0.2
API target karma-chrome-launcher@3.2.0
Supported Node.js See supported framework requirements
License MIT
Main entry index.js
Runtime dependencies which

Installation

npm install @stackline/karma-chrome-launcher

Preserve existing imports and plugin resolution with an npm alias:

npm install karma-chrome-launcher@npm:@stackline/karma-chrome-launcher

Usage and API reference

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

$ npm i -D @stackline/karma-chrome-launcher

Configuration

// karma.conf.js
module.exports = function(config) {
  config.set({
    browsers: ['Chrome', 'Chrome_without_security'], // You may use 'ChromeCanary', 'Chromium' or any other supported browser

    // you can define custom flags
    customLaunchers: {
      Chrome_without_security: {
        base: 'Chrome',
        flags: ['--disable-web-security', '--disable-site-isolation-trials']
      }
    }
  })
}

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

customLaunchers: {
  Chrome_with_debugging: {
    base: 'Chrome',
    chromeDataDir: path.resolve(__dirname, '.chrome')
  }
}

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

$ 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

Usage

$ npm i -D puppeteer karma-chrome-launcher

// karma.conf.js
process.env.CHROME_BIN = require('puppeteer').executablePath()

module.exports = function(config) {
  config.set({
    browsers: ['ChromeHeadless']
  })
}

For more information on Karma see the homepage.

Credits and original authors

Original copyright, license notices and contributor acknowledgements remain part of this distribution. Stackline maintenance does not replace authorship of the original work.

License

MIT. See the license and notice files in the repository.

Community and Links

Use this repository's issue tracker for reproducible bugs and feature requests. Join r/Stackline for examples, usage questions and release discussions.

Upstream issues and maintenance review

Upstream review

Based on karma-chrome-launcher@3.2.0, source e92a2b4c19d43fe47a3322a31f72d2a5bfcf77b0. The registry gitHead source manifest contains the previous semantic-release version, but every upstream published runtime file matches this commit byte-for-byte. Only package metadata differs in the upstream tarball, whose integrity was checked independently.

Issue triage (2026-09-29)

No upstream maintainer was contacted. Runtime files and original license/authorship are retained. Development tooling uses Node24; package engine declarations remain unchanged.

Verification

npm ci --ignore-scripts, npm test, npm run test:package, npm audit --audit-level=low. Packed tests install the actual archive and exercise the exported plugin. Publication uses the exact CI tarball only after CI and CodeQL succeed.

Release changes

Stackline changes

1.0.0

3.2.0 (2023-04-20)

Features

3.1.1 (2022-03-09)

Bug Fixes

3.1.0 (2019-08-13)

Features

3.0.0 (2019-07-12)

Features

2.2.0 (2017-06-23)

Features

2.1.1 (2017-05-05)

Bug Fixes

2.1.0 (2017-05-02)

Features

2.0.0 (2016-08-18)

Features

1.0.1 (2016-05-02)

0.2.3 (2016-03-22)

Features

0.2.2 (2015-12-01)

Bug Fixes

0.2.1 (2015-10-07)

Bug Fixes

<a name"0.2.0">

0.2.0 (2015-06-23)

Bug Fixes

<a name"0.1.9">

0.1.9 (2015-06-23)

<a name"0.1.8">

0.1.8 (2015-06-23)

<a name"0.1.7">

0.1.7 (2015-06-23)

<a name"0.1.6">

0.1.6 (2015-06-23)

Bug Fixes

<a name"0.1.5">

0.1.5 (2015-06-23)

Bug Fixes

<a name"0.1.4">

0.1.4 (2015-06-23)

Bug Fixes

<a name"0.1.3">

0.1.3 (2015-06-23)

Features

<a name"0.1.2">

0.1.2 (2015-06-23)

<a name"0.1.12">

0.1.12 (2015-06-23)

<a name"0.1.11">

0.1.11 (2015-06-23)

<a name"0.1.10">

0.1.10 (2015-06-23)

Bug Fixes

Features

<a name"0.1.1">

0.1.1 (2015-06-23)

Bug Fixes

<a name"0.1.0">

0.1.0 (2015-06-23)

<a name"0.0.2">

0.0.2 (2015-06-23)

Features

Release files and references

Package bytes, npm provenance and the immutable GitHub release were verified for this version. Security checks describe the reviewed release; documented compatibility risks and upstream reports are not blanket claims of resolution.