To help you get started, we've collected the most common ways that karma-chrome-launcher is being used within popular public projects.

SignalR / SignalR / test / Microsoft.AspNet.SignalR.Client.JS.Tests / karma.conf.js View on Github

// Karma configuration
// Generated on Tue Sep 04 2018 11:57:39 GMT-0700 (Pacific Daylight Time)

let browsers = [];

try {
  // Karma configuration for a local run (the default)
  const fs = require("fs");
  const which = require("which");

  // Bring in the launchers directly to detect browsers
  const ChromeHeadlessBrowser = require("karma-chrome-launcher")["launcher:ChromeHeadless"][1];
  const ChromiumHeadlessBrowser = require("karma-chrome-launcher")["launcher:ChromiumHeadless"][1];
  const FirefoxHeadlessBrowser = require("karma-firefox-launcher")["launcher:FirefoxHeadless"][1];
  const FirefoxDeveloperHeadlessBrowser = require("karma-firefox-launcher")["launcher:FirefoxDeveloperHeadless"][1];
  const EdgeBrowser = require("karma-edge-launcher")["launcher:Edge"][1];
  const SafariBrowser = require("karma-safari-launcher")["launcher:Safari"][1];
  const IEBrowser = require("karma-ie-launcher")["launcher:IE"][1];

  function browserExists(path) {
    // On linux, the browsers just return the command, not a path, so we need to check if it exists.
    if (process.platform === "linux") {
      return !!which.sync(path, { nothrow: true });
    } else {
      return fs.existsSync(path);
    }
  }

  function tryAddBrowser(name, b) {

View more ways to use karma-chrome-launcher

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

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

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.