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

import-cleaner

v1.0.1

Published

Tool to scan project files and remove unused import statements

Readme

Import Cleaner

A Node.js tool to scan your project and automatically remove unused import statements.

Installation

# Install globally
npm install -g import-cleaner

# Or locally in your project
npm install --save-dev import-cleaner

Usage

Command Line

# Clean current directory
import-cleaner

# Clean specific directory
import-cleaner ./src

# Dry run (preview without making changes)
import-cleaner --dry-run

# Show detailed information about unused imports
import-cleaner --verbose

# Exclude additional directories
import-cleaner --exclude "temp,output,cache"

# Combine options
import-cleaner ./src --dry-run --verbose

Programmatic Usage

const { cleanUnusedImports } = require("import-cleaner");

const stats = cleanUnusedImports("./src", {
  extensions: [".js", ".jsx", ".ts", ".tsx"], // file extensions to scan
  recursive: true, // scan subdirectories
  dryRun: false, // set to true to preview without changes
  exclude: ["node_modules", ".git", "dist"], // directories to exclude
  verbose: true, // show detailed information
});

console.log(stats);
// {
//   filesScanned: 25,
//   filesModified: 8,
//   totalImportsRemoved: 15,
//   unusedImports: [
//     {
//       file: 'src/components/Button.js',
//       imports: [
//         { name: 'useState', source: 'react', isDefault: false },
//         { name: 'classNames', source: 'classnames', isDefault: true }
//       ]
//     }
//   ]
// }

Features

  • Scans JavaScript and TypeScript files (.js, .jsx, .ts, .tsx)
  • Identifies and removes unused import statements
  • Keeps import statements that are actually used
  • Works with ES6 named and default imports
  • Recursive directory scanning
  • Dry run mode to preview changes
  • Verbose mode to show detailed information about unused imports
  • Automatically excludes node_modules, .git, dist, and build directories

How It Works

Import Cleaner analyzes your code using a two-pass approach:

  1. First pass: Collects all import statements and imported identifiers
  2. Second pass: Tracks which identifiers are actually used in the code
  3. Compares the two to identify unused imports
  4. Removes unused imports while preserving code structure

Limitations

  • Currently doesn't detect imports used only in type annotations
  • Doesn't track dynamic imports or requires
  • May not correctly analyze code with advanced patterns or non-standard usage

License

MIT