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

cleanext

v1.0.3

Published

Advanced interactive tool to detect and clean unused code, components, files, and packages

Readme

CleanExt - Advanced Code Cleanup Tool

An advanced tool to detect and clean unimported components, files, functions, and unused npm packages in your JavaScript/TypeScript project. npm version npm downloads Node.js

Features

  • 🔍 detects unused exports (functions, components, variables)
  • 📁 identifies files that are not imported anywhere
  • 📦 finds npm packages that are installed but not used
  • 🧹 provides options to clean up unused files
  • 🗑️ can uninstall unused npm packages
  • 🖱️ interactive mode for selective cleanup
  • 🎨 new: fully interactive ui with menus and visualizations
  • 👁️ file preview functionality
  • 🌈 colorful and formatted output
  • 💾 export results in multiple formats (json, markdown, html)
  • 🔄 json output for integration with other tools

Installation

# Install globally

npm install -g cleanext

# Or use without installation

npx cleanext

Usage

Basic Usage

# Scan the current directory

cleanext

# Scan a specific directory

cleanext ./src

Interactive Mode

# Launch the fully interactive UI

cleanext --fully-interactive

# Or use the short flag

cleanext -fi

The interactive UI provides:

  • A user-friendly menu system
  • Colorful and formatted output
  • File preview functionality
  • Interactive file and package selection
  • Multiple export formats (JSON, Markdown, HTML)

Advanced Options

# Ignore specific patterns

cleanext --ignore "**/*.stories.tsx" "**/*.test.js"

# Clean up unused files

cleanext --clean

# Uninstall unused packages

cleanext --uninstall

# Interactive mode for selective cleanup

cleanext --interactive --clean --uninstall

# Skip specific checks

cleanext --skip-files --skip-packages

# Output results as JSON

cleanext --json

# Save results to a file

cleanext --output results.json

Running Without npm Installation

# Clone the repository

git clone https://github.com/esmiraldo/cleanext.git cd cleanext

# Install dependencies

npm install

# Build the TypeScript code

npm run build

# Run the tool

node dist/cli.js ./your-project-directory

# Or run in interactive mode

node dist/cli.js --fully-interactive

## How It Works

CleanExt scans your JavaScript and TypeScript files to:

  1. Find all exported functions, classes, and variables
  2. Find all imports across your codebase
  3. Compare the two to identify exports that are never imported
  4. Identify files that are not imported anywhere
  5. Check package.json dependencies against actual imports
  6. Provide options to clean up unused code and packages

## Limitations

  • The tool doesn't track dynamic imports (import())
  • It may not detect imports that use string manipulation or complex patterns
  • It doesn't track usage through re-exports
  • Some false positives may occur for entry point files or components used only in HTML

## License

MIT