npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2026 – Pkg Stats / Ryan Hefner

dev-sweep

v0.2.0

Published

Find and clean node_modules, build caches, and dev artifacts eating your disk

Downloads

98

Readme

dev-sweep

Find and clean node_modules, build caches, and dev artifacts eating your disk. Zero dependencies.

$ npx dev-sweep ~/projects

dev-sweep v0.2.0
Scanning: /home/you/projects (depth: 5)

Found 12 artifacts totaling 4.82 GB:

  SIZE        CAT     TYPE                     PATH
  ------------------------------------------------------------------------------
     1.92 GB  deps    npm/yarn dependencies    /home/you/projects/app/node_modules
   843.2 MB  deps    npm/yarn dependencies    /home/you/projects/site/node_modules
   412.0 MB  build   Next.js build cache      /home/you/projects/app/.next
   ...

  Total: 4.82 GB across 12 items
  847 directories scanned

Install

npx dev-sweep           # run without installing
npm i -g dev-sweep      # or install globally

Usage

dev-sweep                        # scan current directory
dev-sweep ~/projects             # scan specific path
dev-sweep --clean                # scan and offer to delete each match
dev-sweep --dry-run              # show what would be deleted
dev-sweep --ide                  # also check IDE caches (~/.cursor, ~/.vscode, etc)
dev-sweep --sort name            # sort by: size (default), name, type
dev-sweep --json                 # machine-readable JSON output
dev-sweep --category deps        # filter: deps, build, cache, test, logs
dev-sweep -s 0                   # show everything (no size minimum)
dev-sweep -d 10                  # scan deeper (default: 5)

What it finds

Dependenciesnode_modules, .pnpm-store, .yarn, venv, .venv, vendor, bower_components

Build output.next, .nuxt, .angular, .expo, .svelte-kit, dist, build, out, .vercel, target, *.egg-info

Caches.turbo, .cache, .parcel-cache, .vite, .eslintcache, .tsbuildinfo, __pycache__, .pytest_cache, .mypy_cache, .ruff_cache, .gradle

Test/coveragecoverage, .nyc_output, storybook-static

Logsnpm-debug.log, yarn-error.log, yarn-debug.log

IDE (with --ide) — .cursor, .vscode, .config/Code, .config/Cursor

JSON output

dev-sweep --json | jq '.results[] | select(.sizeMB > 100)'

Pipe to other tools, build dashboards, or automate cleanup.

Safety

  • Never deletes anything without --clean flag
  • Interactive per-item confirmation when cleaning
  • IDE caches are always skipped during clean (delete manually)
  • --dry-run shows what would be deleted without touching anything
  • Zero dependencies, zero network calls

License

MIT