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

@satpolo/dev-tree

v1.0.6

Published

A simple, fast, and customizable command-line tool to generate a directory tree for any given path.

Readme

dev-tree

A simple, fast, and customizable command-line tool to generate a directory tree for any given path.

  • Ignores ".git" and "node_modules" by default

Example Output

Running dev-tree in a sample project will produce output like this:

/node-cli-project
│
├──/assets
│  └──/depth1
│  │  ├──depth1.txt
│  │  └──/depth2
│  │  │  ├──depth2.txt
│  │  │  └──/depth3
│  │  │  │  └──/depth4
│  │  │  │  │  ├──/depth5
│  │  │  │  │  └──/hello
├──/routes
│  ├──/stats
│  ├──test.js
│  └──visualize.json
│
├──buildTree.js
├──cli.js
├──package-lock.json
├──package.json
└──validatePath.js

 9 directories, 9 files

Installation

Install the dev-tree tool globally using npm to use it from anywhere in your terminal.

npm install -g @satpolo/dev-tree

Usage

Run the dev-tree command with an optional path to a directory. If no path is provided, it will default to the current working directory.

dev-tree [path] [options]

Options

| Option | Alias | Description | Example | | :--- | :--- | :--- | :--- | | --all | -a | Show hidden files and directories, including .git and node_modules which are ignored by default. | dev-tree --all | | --ignore | -i | Ignore specific dirent names or file extensions. Can be used multiple times. | dev-tree -i .txt node_modules | | --depth | -d | Limit the depth of the directory tree to a specific number (0-indexed). | dev-tree -d 2 | | --output | -o | Save the output to a specified file path instead of printing to the console. | dev-tree -o output.txt |


Examples

Generate a tree for the current directory, ignoring .txt and assets:

dev-tree --ignore .txt --ignore assets

Generate a tree for a specific path, limiting the depth to 3:

dev-tree /home/user/my-project --depth 3

Show all files, including hidden ones, and save the output to a file:

dev-tree --all --output tree.log

License

This project is licensed under the MIT License.