See also http://github.com/js-reporters/js-reporters/issues/116. The issue has been fixed in js-reporters 2.0.