Unused Dependencies Audit & Removal

To remove unused dependencies, the Skill scans your codebase for import and require statements, cross-references them against package.json, and deletes unused packages one-by-one. It regenerates lockfiles and validates the build to ensure no regressions occur.

Yes, the unused dependencies audit supports multiple package managers including npm, Yarn, and pnpm. It cross-references imports across the codebase and regenerates the corresponding lockfiles after safely removing each unused package.

The safest way to prune unused npm packages is through one-by-one removals paired with build validation. This approach performs atomic commits and allows manual review for high-risk or ambiguous packages, ensuring your working build command confirms integrity.

Cross-reference logic identifies unused dependencies by analyzing import and require statements across your source code and matching them against the packages declared in package.json. Packages not referenced in any import statements are flagged as unused.

A working build command is required to validate build integrity after each one-by-one dependency removal. This ensures that removing an unused package does not introduce regressions, confirming that the remaining dependencies and codebase still compile and function correctly.

Automated removal limitations include ambiguous packages that require manual review and high-risk dependencies needing atomic commits. The process relies entirely on static import and require analysis, meaning dynamically imported or referenced packages might still need human oversight.