Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

david blame - which of my deps have recent, declared-range-qualifying, updates #69

Open
olizilla opened this issue Feb 10, 2015 · 0 comments

Comments

@olizilla
Copy link
Collaborator

You know when you checkout a project and it builds fine for all the incumbent developers and is all build errors for you. Like when someone drops a patch release that meets the requirements of your package.json, but actually changes something fairly major.

All your fellow devs look at you like a newb, while you insist meekly that you followed the readme.

DAVID TO THE RESCUE... "David, based on my package.json show me all deps that published updates recently, that meet our declared semver range requirements. WHICH SEMVER TORPEDO HAS BESMIRCHED OUR PROJECT?"

david blame --month

where the default is "changes in the last week" and flags allow you to alter the amount of history you wanna blame against.

Leaderboards of most projects besmirched by module is a nice to have extension.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant