CLI: Return a nonzero exit code when dependencies out of date #42

fabiosantoscode opened this Issue Mar 6, 2014 · 3 comments


None yet
2 participants


I'm trying to use the david command in Jenkins, to integrate it with the CI workflow.

I noticed that it always returns 0, even though some dependencies (in my case devDependencies) are out of date.

@alanshaw alanshaw added enhancement bug and removed enhancement labels Mar 6, 2014


alanshaw commented Mar 6, 2014

hmmm. It's not strictly an error. What do you think about passing a flag to enable this behaviour?

alanshaw removed the bug label Mar 6, 2014

Sounds good to me. --error=all to fail on any outdated dependencies, --error=production to ignore devDependencies but fail on {dev,optional,peer}Dependencies?

I don't see how to address the "Pinned, out of date" (yellow on the badges) situation, though.


alanshaw commented Dec 19, 2014

I thought about this a bit more and I think exiting with an error code when dependencies are out of date is more the expected behaviour. Will implement this.

alanshaw closed this in 3c3599a Dec 19, 2014

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment