Heads Up! You're viewing the docs for v6.3, an old version of Karma. v6.4 is the newest.


Preprocessors in Karma allow you to do some work with your files before they get served to the browser. These are configured in the preprocessors block of the configuration file:

preprocessors: {
  '**/*.coffee': ['coffee'],
  '**/*.tea': ['coffee'],
  '**/*.html': ['html2js']


There are multiple expressions referencing the "coffee" preprocessor in this example, as a preprocessor can be listed more than once as another way to specify multiple file path expressions.


Most of the preprocessors need to be loaded as plugins.

Available Preprocessors #

Here's an example of how to add the CoffeScript preprocessor to your testing suite:

# Install it first with npm
$ npm install karma-coffee-preprocessor --save-dev

And then inside your configuration file...

module.exports = function(config) {
    preprocessors: {
      '**/*.coffee': ['coffee']

Of course, you can write custom plugins too!

Configured Preprocessors #

Some of the preprocessors can also be configured:

coffeePreprocessor: {
  options: {
    bare: false

Or define a configured preprocessor:

customPreprocessors: {
  bare_coffee: {
    base: 'coffee',
    options: {bare: true}

Mini matching #

The keys of the preprocessors config object are used to filter the files specified in the files configuration.

  • First the file paths are expanded to an absolute path, based on the basePath configuration and the directory of the configuration file. See files for more information on that.
  • Then the newly expanded path is matched using minimatch against the specified key.

So for example the path /my/absolute/path/to/test/unit/file.coffee matched against the key **/*.coffee would return true, but matched against just *.coffee it would return false and the preprocessor would not be executed on the CoffeeScript files.

Order of execution #

If a file matches only one key in the preprocessors config object, then karma will execute the preprocessors over that file in the order they are listed in the corresponding array. So for instance, if the config object is:

preprocessors: {
  '*.js': ['a', 'b']

Then karma will execute 'a' before executing 'b'.

If a file matches multiple keys, karma will use the config.preprocessor_priority map to control the execution order. The config.preprocessor_priority should be an object with property names equal to the preprocessor names and property values equal to the priority of execution. Higher priority preprocessors are run earlier. The default priority is 0.

If this config option is not set, karma will do its best to execute the preprocessors in a reasonable order. So if you have:

preprocessors: {
  '*.js': ['a', 'b'],
  'a.*': ['b', 'c']

then for a.js, karma will run 'a' then 'b' then 'c'. If two lists contradict each other, like:

preprocessors: {
  '*.js': ['a', 'b'],
  'a.*': ['b', 'a']

then karma will arbitrarily pick one list to prioritize over the other. In a case like:

preprocessors: {
  '*.js': ['a', 'b', 'c'],
  'a.*': ['c', 'b', 'd']

Then 'a' will definitely be run first, 'd' will definitely be run last, but it's arbitrary if karma will run 'b' before 'c' or vice versa.