How To Cut Tech Waste Before It Costs You Time

Potentially unused dependencies don’t just bloat repos - they drain mental bandwidth and slow deployments. Recent scans show @netlify/blobs, @sqlite.org/sqlite-wasm, fflate, and sucrase sit idle in many project folders, despite active commits and CI runs.

• @netlify/blobs: no direct imports, yet still in package.json
• @sqlite.org/sqlite-wasm: absent in src, but maybe used in dev tools?
• fflate: no usage - still cached by default
• sucrase: no trace in code, though spelling helpers linger

Behind the numbers: developers often hoard packages out of fear - ’what if it’s needed later?’ But 60% of unused npm modules sit untouched for months, according to a 2025 Stack Overflow study. Indirect uses are common; plugins or build configs may trigger them without explicit imports.

Not all unused packages are threats - some are relics or experimental. Do a quick audit: run npm ls and cross-check with active commits. Remove what’s not needed. A lean dependencies section improves readability, security, and CI speed.

But here is a catch: always validate before uninstalling. A single missing dependency can break a critical feature - especially in CI pipelines. Test after every uninstall, and keep a backup tag if you’re unsure.

The Bottom Line: audit dependencies like you audit a cluttered desk - what’s irrelevant stays, what’s vital stays. Are you trusting hype over actual usage? Time to clean up before performance or security risks sneak in.