You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
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?"
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.
The text was updated successfully, but these errors were encountered: