dependency-cleanup

Dependency Cleanup

Bloated dependencies slow down builds, increase security surface area, and complicate updates.

Audit: Review package.json, requirements.txt, or Cargo.toml.
Verify Usage: For any suspect dependency, perform a global search across the codebase (e.g., import .* from 'lodash').
Remove: If there are zero usages, use the native package manager command to remove it (e.g., npm uninstall lodash or pip uninstall ...). Do not just manually edit the manifest unless absolutely necessary, to ensure lockfiles are updated correctly.
Consolidate: If multiple libraries serve the exact same purpose (e.g., moment and date-fns), flag it to the user for future consolidation. Do not attempt a massive library migration autonomously.
Validate: Run the build and test suite to ensure the removed dependency wasn't implicitly required by a build script or runtime environment.

Bloated dependencies slow down builds, increase security surface area, and complicate updates.

Audit: Review package.json, requirements.txt, or Cargo.toml.
Verify Usage: For any suspect dependency, perform a global search across the codebase (e.g., import .* from 'lodash').
Remove: If there are zero usages, use the native package manager command to remove it (e.g., npm uninstall lodash or pip uninstall ...). Do not just manually edit the manifest unless absolutely necessary, to ensure lockfiles are updated correctly.
Consolidate: If multiple libraries serve the exact same purpose (e.g., moment and date-fns), flag it to the user for future consolidation. Do not attempt a massive library migration autonomously.
Validate: Run the build and test suite to ensure the removed dependency wasn't implicitly required by a build script or runtime environment.