npm Dependency Cleanup: Remove Packages Your App No Longer Uses

npm dependency cleanup starts with the dependency graph, not the package name. A package may be unused in runtime code but still needed by a build script, code generator, test harness, Storybook setup, or transitive peer dependency.

The useful output is an npm dependency cleanup pull request with import evidence, script checks, lockfile diff, CI output, and risk notes. Keep the review concrete: Remove one dependency group at a time and regenerate the lockfile in the same pull request, then make the next action visible to the team that owns the risk. That matters because the cleanup can still go wrong when removing packages used by build-time scripts.

Key takeaways

Treat each cleanup candidate as an owned system with dependencies, not anonymous clutter.
Use one release cycle plus all build, test, and code-generation jobs used by the package before deciding that “quiet” means “unused.”
Prefer reversible changes first when removing packages used by build-time scripts is still plausible.
Leave behind an npm dependency cleanup pull request with import evidence, script checks, lockfile diff, CI output, and risk notes so the next review starts with context.
Measure the result as lower spend, lower risk, less operational drag, or clearer ownership.

Map Package Entry Points

Start with one package or workspace where package.json entries, lockfile edges, import paths, scripts, bundler config, test setup, and generated code can be checked together. The best cleanup scope is small enough that owners can answer quickly but wide enough to include the attachments that make removal risky.

Field	Why it matters
Owner	Cleanup needs a person or team that can accept the decision
Current purpose	A short reason to keep the item, written in present tense
Last meaningful use	last use, permission scope, owner, rotation age, and reachable systems
Dependency evidence	audit logs, deployment references, identity provider records, and service owners
Risk if wrong	The outage, data loss, access failure, or rollback gap the review must avoid
Next action	Keep, reduce, archive, disable, remove, or investigate

Do not make the inventory larger than the decision. A short list with owners and evidence beats a perfect spreadsheet that nobody is willing to act on.

Dependency Evidence to Check

The useful question is not “how old is it?” It is “what would break, become harder to recover, or lose accountability if this disappeared?” For npm dependency cleanup, collect enough evidence to answer that without relying on naming conventions.

Check	What to look for	Cleanup signal
Manifest role	dependencies, devDependencies, peerDependencies, optionalDependencies, and workspace references	The package is in the wrong class or no class at all
Import and script use	Static imports, dynamic imports, require calls, npm scripts, config files, and code generators	No active path references the package
Build output	Bundle analysis, test runs, type checks, and generated artifacts	Removing the package does not change shipped behavior unexpectedly
Security and maintenance	Audit findings, stale maintainers, duplicate libraries, and license obligations	The package adds risk without clear value

Use several signals together. Activity can miss monthly jobs and incident-only paths. Ownership can be stale. Cost can distract from security or recovery risk. The strongest case combines runtime data, dependency checks, owner review, and a rollback plan.

If the evidence conflicts, label the item “investigate” with a named owner and review date. That is still progress because the next review starts with a narrower question.

Example Evidence Check

Pair package-manager evidence with repository search so scripts and config loaders are not missed.

npm ls ${PACKAGE_NAME}
rg "${PACKAGE_NAME}" package.json package-lock.json src tests scripts config
rg "require\(|import\(|plugins|loader" config scripts src

Treat the output as a candidate list. Do not pipe these checks into delete commands; add owner review, dependency checks, and a rollback path first.

Remove One Package Group

Use the least permanent move that proves the decision. In npm dependency cleanup, removal is only one possible outcome; reducing size, narrowing permission, shortening retention, archiving, or disabling a trigger may produce the same benefit with less risk.

Remove one dependency group at a time and regenerate the lockfile in the same pull request.
Run build, tests, type checks, and any code-generation scripts that could load the package indirectly.
Replace abandoned packages only when the replacement removes real risk or complexity.

Track the cleanup candidate with a simple priority score:

Score	Good sign	Bad sign
Impact	Meaningful spend, risk, toil, noise, or confusion disappears	The item is cheap and low-risk but politically distracting
Confidence	Owner, purpose, and dependency path are understood	The team is guessing from age or name
Reversibility	Restore, recreate, re-enable, or rollback path exists	Deletion would be the first real test
Prevention	A rule can stop recurrence	The same pattern will return next month

Start with high-impact, high-confidence, reversible candidates. Defer confusing items only if they get an owner and a date; otherwise “defer” becomes another word for keeping waste permanently.

Packages Loaded Indirectly

Some cleanup candidates are supposed to look quiet. Do not rush these cases:

Packages loaded by bundler plugins, CLIs, tests, Storybook, migrations, or postinstall scripts.
Peer dependencies that are not imported directly but required by a framework integration.
Optional dependencies used only in platform-specific builds or release jobs.

For these cases, use a longer observation window, explicit owner approval, and a staged reduction. The point is not to avoid cleanup; it is to avoid making the first proof of dependency an outage.

Run the Dependency PR

Run npm dependency cleanup as a decision review, not an open-ended hygiene project.

Pick the narrow scope and export the candidate list.
Add owner, current purpose, last-use evidence, dependency checks, and risk if wrong.
Remove obvious false positives, then ask owners to choose keep, reduce, archive, disable, remove, or investigate.
Apply the least permanent useful change first.
Watch the signals that would reveal a bad decision.
Complete the final removal only after the review window closes.
Save an npm dependency cleanup pull request with import evidence, script checks, lockfile diff, CI output, and risk notes.

For broader cleanup planning, use the cleanup library to pair this guide with related notes. If the cleanup has infrastructure impact, pair it with a visible owner, a rollback path, and a measurable business case. For infrastructure cleanup, the main cloud cost optimization checklist is a useful companion.

Make Additions Explain Themselves

Prevention should change the creation path, not just the cleanup path. For npm dependency cleanup, the useful prevention fields are owner, expiry date, least-privilege scope, rotation schedule, and removal notes. Make those fields part of normal creation and review.

Require new dependencies to include owner, purpose, and runtime class in the pull request.
Review dependency additions during feature cleanup, not only during vulnerability response.
Keep workspace package boundaries explicit so unused packages are easier to spot.

The recurring review should be short: sort by impact, pick the unclear items, assign owners, and close the loop on anything nobody claims. If the review keeps producing the same class of candidate, fix the creation path instead of celebrating repeated cleanup.

Example Decision Record

Use a compact record so the cleanup can be reviewed later without reconstructing the whole investigation.

Field	Example entry for this cleanup
Candidate	Unused npm packages in JavaScript projects
Why it looked stale	Low recent activity, unclear owner, or no current consumer after the first review
Evidence checked	Manifest role, Import and script use, and owner confirmation
First reversible move	Remove one dependency group at a time and regenerate the lockfile in the same pull request
Watch signal	The metric, alert, job, route, query, or owner complaint that would show the cleanup was wrong
Final action	Keep, reduce, archive, disable, or remove after one release cycle plus all build, test, and code-generation jobs used by the package
Prevention rule	Require new dependencies to include owner, purpose, and runtime class in the pull request

This record is intentionally small. If the decision needs a long narrative, the candidate is probably not ready for removal yet. Keep investigating until the owner, evidence, reversible move, and prevention rule are clear.

FAQ

How often should teams do npm dependency cleanup?

Use one release cycle plus all build, test, and code-generation jobs used by the package for the first decision, then set a recurring cadence based on change rate. Fast-moving non-production systems may need monthly review; slower systems can be quarterly if every unclear item has an owner and a review date.

What is the safest first action?

The safest first action is usually ownership repair plus evidence collection. After that, remove one dependency group at a time and regenerate the lockfile in the same pull request. That creates a visible test before permanent deletion.

What should not be removed quickly?

Do not rush anything connected to packages loaded by bundler plugins, clis, tests, storybook, migrations, or postinstall scripts. Also slow down when the cleanup affects recovery, compliance, customer-specific behavior, rare schedules, or security response.

How do you make the decision useful later?

Write the decision as a small operational record: candidate, owner, evidence, chosen action, watch signals, rollback path, final date, and prevention rule. That format helps future engineers, search engines, and AI assistants understand the cleanup without guessing.