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

@avinashchby/devclean

v0.1.1

Published

Universal build artifact cleaner — reclaim hundreds of GB from build artifacts you forgot about

Readme

devclean

Reclaim hundreds of GB from build artifacts you forgot about.

A universal CLI tool that scans your projects for build artifacts, caches, and dependency folders — then helps you clean them safely.

Quick Start

npx devclean

No install required. Scans your current directory and lets you pick what to remove.

How It Works

  1. Scan — Recursively walks your project directories looking for known build artifacts
  2. Report — Shows what was found, grouped by language, sorted by size
  3. Select — Interactive picker lets you choose exactly what to remove
  4. Clean — Deletes selected artifacts and reports freed space

Supported Languages

| Language | Artifacts | Project File Required | |---|---|---| | JavaScript/TypeScript | node_modules, .next, .nuxt, dist, build, .output, .parcel-cache, .turbo, .angular/cache, .svelte-kit | package.json | | Rust | target | Cargo.toml | | Python | venv, .venv, __pycache__, .mypy_cache, .pytest_cache, .ruff_cache, *.egg-info | requirements.txt / pyproject.toml / setup.py | | Go | vendor | go.mod | | Java/Kotlin | .gradle, build, target, .idea | build.gradle / pom.xml | | C/C++ | build, cmake-build-*, _build | CMakeLists.txt / Makefile | | Ruby | vendor/bundle | Gemfile | | PHP | vendor | composer.json | | .NET | bin, obj | *.csproj | | General | .cache, .tmp, coverage, .terraform | (none) |

Artifacts are only flagged when the corresponding project file is found in the parent directory (except General artifacts). This prevents false positives.

CLI Options

Usage: devclean [options] [path]

Arguments:
  path                  directory to scan (default: current working directory)

Options:
  --scan                scan and report only, do not clean
  --auto                auto-clean all pre-selected artifacts
  --dry-run             show what would be deleted without deleting
  --days <number>       minimum age in days for auto-selection (default: 30)
  --type <types>        filter by artifact types (comma-separated)
  --min-size <mb>       minimum size in MB to include
  --sort <criterion>    sort by "size" or "age" (default: size)
  --json                output results as JSON
  --protect <paths>     comma-separated paths to never delete
  -V, --version         output the version number
  -h, --help            display help

Examples

# Scan only, don't delete anything
npx devclean --scan

# Auto-clean artifacts older than 60 days
npx devclean --auto --days 60

# Preview what would be deleted
npx devclean --auto --dry-run

# Only show Rust and Python artifacts
npx devclean --type rust,python

# Scan a specific directory, ignore artifacts under 100 MB
npx devclean ~/Projects --min-size 100

# Output as JSON for scripting
npx devclean --scan --json

# Protect specific paths from deletion
npx devclean --protect ~/Projects/important-app/node_modules

Global Cache Cleaning

Clean global tool caches (npm, yarn, pnpm, pip, cargo, Go) with:

npx devclean cache

Detects caches for: npm, yarn, pnpm, Go build, pip, and cargo registry.

Use --dry-run to preview without deleting:

npx devclean cache --dry-run

Config File

Create ~/.devclean.json to set persistent preferences:

{
  "protect": [
    "~/Projects/production-app/node_modules",
    "~/Projects/active-service/target"
  ],
  "autoCleanDays": 30,
  "scanPaths": [],
  "ignorePaths": [
    "~/Archive"
  ],
  "customArtifacts": []
}

| Key | Type | Description | |---|---|---| | protect | string[] | Paths that will never be deleted | | autoCleanDays | number | Default age threshold for --auto mode | | scanPaths | string[] | Additional directories to scan | | ignorePaths | string[] | Directories to skip during scanning | | customArtifacts | array | User-defined artifact patterns |

Paths support ~ expansion for the home directory.

Safety Guarantees

devclean is designed to be safe by default:

  • Smart detection — Artifacts are only identified when a matching project file (e.g., package.json, Cargo.toml) exists in the parent directory. No guessing.
  • Protect list — Mark paths as protected in config or via --protect to permanently exclude them from cleaning.
  • .git skipping — Anything inside a .git directory is automatically excluded.
  • System path protection — System directories (/usr, /etc, /home, etc.) and the home directory itself can never be deleted.
  • No source code deletion — Only known build artifact and cache directories are targeted. Source files are never touched.
  • Interactive by default — You always confirm before anything is deleted, unless you explicitly opt into --auto mode.
  • Dry run support — Use --dry-run to see exactly what would happen without making any changes.

Requirements

  • Node.js >= 18.0.0

License

MIT