A command-line tool to check for outdated, incorrect, and unused npm dependencies with interactive updates.
npm-check is a command-line tool that analyzes npm dependencies in Node.js projects. It checks for outdated packages, identifies unused dependencies, and provides an interactive way to update them safely. It solves the problem of manual dependency maintenance and reduces bloat in package.json.
Node.js developers and teams who need to keep their project dependencies up-to-date and clean, especially those working on multiple projects or in CI/CD environments.
Developers choose npm-check for its comprehensive analysis, interactive update interface, and support for various registries. It improves over npm's built-in outdated command by adding unused dependency detection and a safer, more user-friendly update process.
Check for outdated, incorrect, and unused dependencies.
Open-Awesome is built by the community, for the community. Submit a project, suggest an awesome list, or help improve the catalog on GitHub.
Identifies packages with newer versions available and provides links to documentation, helping developers make informed update decisions, as shown in the README's feature list.
Offers a user-friendly UI with the -u flag for selectively updating packages, reducing typos and manual errors, demonstrated in the interactive gif and options section.
Integrates with depcheck to flag modules not referenced in code, supporting ES6 import syntax, as mentioned in the features and specials option.
Works with public npm, private registries, Sinopia, and supports npm@2, npm@3, ied, pnpm, detailed in the registry flexibility and installer options.
Unlike npm audit, npm-check does not scan for known security vulnerabilities in dependencies, requiring separate tools for comprehensive safety, a missing feature not addressed in the README.
Unused dependency detection relies on depcheck, which can have false positives or miss complex usage patterns, as noted in the integration and specials options for config files.
Requires Node >= 10.9.0, which may exclude projects stuck on older Node versions for compatibility reasons, as stated in the requirements section.