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

clean-tree

v1.0.2

Published

A modern, TypeScript-based implementation of the `tree` command with advanced filtering and .gitignore support.

Readme

clean-tree

A modern, TypeScript-based implementation of the tree command with advanced filtering and .gitignore support.

Features

  • 🌳 Beautiful tree visualization - Clean, colorized directory structure display
  • 📏 Depth limiting - Control how deep to traverse with --depth
  • 🚫 Pattern exclusion - Exclude files/directories with glob patterns
  • 📝 .gitignore support - Respect .gitignore rules automatically
  • 📝 .*ignore support - Respect .*ignore rules automatically for LLM inputs
  • 🎨 Colorized output - Directories and files are color-coded for better readability
  • Fast & lightweight - Efficient traversal with minimal dependencies
  • 🔧 Cross-platform - Works on Windows, macOS, and Linux

Installation

Global Installation (Recommended)

npm install -g clean-tree

Local Installation

npm install clean-tree
npx clean-tree

Usage

Basic Usage

# Display current directory tree
clean-tree

# Display specific directory
clean-tree /path/to/directory

Advanced Options

# Limit depth to 2 levels
clean-tree --depth 2

# Respect .gitignore rules
clean-tree --gitignore

# Exclude specific patterns
clean-tree --exclude "node_modules"

# Respect all .*ignore files
clean-tree --allignore

# Combine multiple options
clean-tree src --depth 3 --allignore --exclude "*.log"

Command Line Options

| Option | Alias | Type | Description | |--------|-------|------|-------------| | --depth | -d | number | Maximum depth to display (default: unlimited) | | --exclude | -e | string | Exclude files/directories matching glob pattern | | --gitignore | -g | boolean | Respect .gitignore rules (default: false) | | --allignore | -a | boolean | Respect all .*ignore files (e.g., .gitignore, .npmignore, .dockerignore) | | --help | -h | boolean | Show help information |

Examples

Basic Tree Display

clean-tree

Output:

my-project
├── src
│   ├── components
│   │   ├── Header.tsx
│   │   └── Footer.tsx
│   ├── utils
│   │   └── helpers.ts
│   └── index.ts
├── package.json
└── README.md

4 directories, 6 files

With Depth Limitation

clean-tree --depth 2

Output:

my-project
├── src
│   ├── components
│   ├── utils
│   └── index.ts
├── package.json
└── README.md

3 directories, 3 files

Respecting .gitignore

clean-tree --gitignore

This will automatically exclude files and directories listed in your .gitignore file.

Excluding Patterns

clean-tree --exclude "node_modules"
clean-tree --exclude "*.log"
clean-tree --exclude "{dist,build}"

Pattern Matching

The --exclude option supports glob patterns:

  • * - matches any number of characters
  • ? - matches a single character
  • ** - matches directories recursively
  • {pattern1,pattern2} - matches either pattern
  • [abc] - matches any character in brackets

Examples:

# Exclude all JavaScript files
clean-tree --exclude "*.js"

# Exclude multiple directories
clean-tree --exclude "{node_modules,dist,build}"

# Exclude all hidden files
clean-tree --exclude ".*"

.gitignore Integration

When using the --gitignore flag, clean-tree will:

  1. Look for a .gitignore file in the target directory
  2. Parse the gitignore patterns
  3. Automatically exclude matching files and directories
  4. Apply the same rules as Git would

This is particularly useful for development projects where you want to see the project structure without build artifacts, dependencies, or temporary files.

Requirements

  • Node.js >= 14.0.0
  • npm >= 6.0.0

Development

Building from Source

# Clone the repository
git clone https://github.com/your-username/clean-tree.git
cd clean-tree

# Install dependencies
npm install

# Build the project
npm run build

# Run locally
npm run dev

Scripts

  • npm run build - Compile TypeScript to JavaScript
  • npm run dev - Run with ts-node for development
  • npm start - Run the compiled JavaScript version
  • npm run watch - Watch for changes and rebuild

Contributing

Contributions are welcome! Please feel free to submit a Pull Request. For major changes, please open an issue first to discuss what you would like to change.

  1. Fork the repository
  2. Create your feature branch (git checkout -b feature/amazing-feature)
  3. Commit your changes (git commit -m 'Add some amazing feature')
  4. Push to the branch (git push origin feature/amazing-feature)
  5. Open a Pull Request

License

This project is licensed under the MIT License - see the LICENSE file for details.

Support

If you encounter any issues or have questions:

  1. Check the Issues page
  2. Create a new issue if your problem isn't already reported
  3. Provide as much detail as possible, including:
    • Your operating system
    • Node.js version
    • Command you ran
    • Expected vs actual output