npm-update-report

Run the tool after updating dependencies in package.json to automatically generate a changelog investigation report. It detects version changes, researches package changelogs, verifies build scripts (lint, typecheck, test, build), and outputs a structured markdown report to ./reports/{date}-{branch-name}.md with impact assessment.

Yes, the tool supports monorepos and multi-package projects. It syncs versions across package.json files against lockfiles, detects major and minor bumps in frameworks and build tools, and generates a consolidated report across your entire project scope.

The tool runs four verification steps after analyzing changes: lint validation, typecheck, test execution, and build verification. These checks confirm that dependency updates don't break your project and provide confidence in the update's safety before deployment.

The tool maintains semantic versioning prefixes during synchronization between package.json and lockfile. It respects existing version constraints while detecting and reporting major and minor version changes, ensuring your versioning strategy remains intact.

The markdown report includes extracted changes from package.json, changelog research findings, verification results from lint/typecheck/test/build, and structured impact assessment. Output locations follow the pattern ./reports/{yyyyMMdd}-{branch-name}.md for easy tracking and review.

Yes, the tool specifically targets frameworks and build tools by detecting major and minor version bumps in these categories. It prioritizes changelog research for key packages in your stack and evaluates impact in the context of how those tools are used in your project.