I kept running into a problem where stuff I commited did not work on a build machine or someone else's computer, and quite often the problem turned out to be that my npm dependencies had changed.
To repair the issue, I made this small tool that allows you to keep track of those changes to immediately see what might have caused the issues.
To install the CLI:
$ npm install -g depdiff
The CLI features two commands, list-dependencies and list-changes. list-dependencies lists your dependencies as JSON, going through your bower.json and package.json files. list-changes takes a file of this JSON format and compares it to the current situation, showing a diff similar to what you might be used to in your version control.
To save the current state to a file:
$ depdiff list-dependencies > current-deps.json
To compare current state to an older state:
$ depdiff list-changes old-deps.json
FAQs
A CLI tool to check dependency changes between project versions.
We found that depdiff demonstrated a not healthy version release cadence and project activity because the last version was released a year ago. It has 1 open source maintainer collaborating on the project.
Did you know?
Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.
Security News
Multiple high-impact npm maintainers confirm they have been targeted in the same social engineering campaign that compromised Axios.
Security News
Axios compromise traced to social engineering, showing how attacks on maintainers can bypass controls and expose the broader software supply chain.
Security News
Node.js has paused its bug bounty program after funding ended, removing payouts for vulnerability reports but keeping its security process unchanged.