I'm working on a project that defines its karma options in a karma.conf.js file. When client.captureConsole is defined in the karma config, it gets ignored when I run grunt karma. However, if the option is defined in the Gruntfile instead, it works. I know that client.captureConsole is valid in the config file because I can run karma directly with that config property set, and it works as expected.

It looks like grunt-karma is setting defaults for the client options (here) if they are not set in the Gruntfile options object. My suspicion is that these defaults eventually override the settings from karma.conf.js, causing the behavior I'm seeing.

Is there a reason why the client options are directly being set by grunt-karma? If these are really karma defaults, shouldn't karma take care of setting them?