Version 1.1.3 of pre-commit just got published.

This version is covered by your current version range and after updating it in your project the build failed.

As pre-commit is “only” a devDependency of this project it might not break production or downstream projects, but “only” your build or test tools – preventing new deploys or publishes.

I recommend you give this issue a high priority. I’m sure you can resolve this 💪

Your Greenkeeper Bot 🌴

Version 1.2.2 of pre-commit just got published.

This version is covered by your current version range and after updating it in your project the build failed.

As pre-commit is “only” a devDependency of this project it might not break production or downstream projects, but “only” your build or test tools – preventing new deploys or publishes.

I recommend you give this issue a high priority. I’m sure you can resolve this 💪

Your Greenkeeper Bot 🌴

Hi there,

I found an issue in the code because null checks are not enforced. Namely the code assumes that, match object from the RegEx, will contain an element at the position 3 (or match[2] ) which can be null and therefore throws an exception when trying to read a property from null.

This test verifies the problem :

  it('should enforce null checks /(null checks not enforced.)', function(){
    assume(function () { ms("000") }).to.throw('Cannot read property \'toLowerCase\' of undefined');
  });

and the fix is to add a null check in line 55 :

if (match[2]== undefined) return 0;

In CoffeeScript it would be even easier since the existential operator "?" which would make the code easier to write.

A more complete (and better solution would be)

if (match[2] == null) { return 0; }

Version 3.4.2 of mocha just got published.

This version is covered by your current version range and after updating it in your project the build failed.

As mocha is “only” a devDependency of this project it might not break production or downstream projects, but “only” your build or test tools – preventing new deploys or publishes.

I recommend you give this issue a high priority. I’m sure you can resolve this 💪

Your Greenkeeper Bot 🌴

Version 1.5.2 of assume just got published.

This version is covered by your current version range and after updating it in your project the build failed.

As assume is “only” a devDependency of this project it might not break production or downstream projects, but “only” your build or test tools – preventing new deploys or publishes.

I recommend you give this issue a high priority. I’m sure you can resolve this 💪

Your Greenkeeper Bot 🌴