CARVIEW |
Select Language
HTTP/2 200
server: GitHub.com
content-type: text/html; charset=utf-8
last-modified: Mon, 29 Jul 2024 17:43:22 GMT
access-control-allow-origin: *
etag: W/"66a7d4ba-26ff"
expires: Fri, 10 Oct 2025 21:35:36 GMT
cache-control: max-age=600
content-encoding: gzip
x-proxy-cache: MISS
x-github-request-id: E119:3B0BAF:108BF:156B7:68E979D0
accept-ranges: bytes
age: 0
date: Fri, 10 Oct 2025 21:25:36 GMT
via: 1.1 varnish
x-served-by: cache-bom-vanm7210022-BOM
x-cache: MISS
x-cache-hits: 0
x-timer: S1760131537.681645,VS0,VE296
vary: Accept-Encoding
x-fastly-request-id: edad8f9e48033a445d46a42e73598af2e5498057
content-length: 2816
Karma - Plugins
Heads Up! You're viewing the docs for v0.10, an old version of Karma.
v6.4 is the newest.
Plugins
Karma can be easily extended through plugins. In fact, all the existing preprocessors, reporters, browser launchers and frameworks are also plugins.
Installation #
Karma plugins are NPM modules, so the recommended way is to keep all the plugins your project requires in package.json
:
{
"devDependencies": {
"karma": "~0.10",
"karma-mocha": "~0.0.1",
"karma-growl-reporter": "~0.0.1",
"karma-firefox-launcher": "~0.0.1"
}
}
Therefore, a simple way how to install a plugin is
npm install karma-<plugin name> --save-dev
Loading Plugins #
By default, Karma loads all NPM modules that are siblinks to it and their name matches karma-*
.
You can also explicitly list plugins you want to load via the plugins
configuration setting. The configuration value can either be
a string (module name), which will be required by Karma, or an object (inlined plugin).
plugins: [
// these plugins will be require() by Karma
'karma-jasmine',
'karma-chrome-launcher'
// inelined plugins
{'framework:xyz', ['factory', factoryFn]},
require('./plugin-required-from-config')
]
There are already many existing plugins. Of course, you write your own plugins too!