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

@andrerodrigo/path-tracer

v1.0.2

Published

CLI tool to quickly trace file paths

Readme

🔍 Path Tracer 🔍

This script automates the process of locating and writing paths for a list of specified components/files within your project directory structure. :file_folder: It's particularly useful when you need to document paths of certain components in your project's directory, instead of doing it manually.

Prerequisites

Before you begin, make sure you have Node.js installed on your machine.

Installation

You can install this tool via npm:

npm i -g @andrerodrigo/path-tracer

Usage

To use the script, follow these steps:

  1. Open your terminal.

  2. Navigate to the directory containing the script and run the following command:

    path-tracer [componentName1.ex] [componentName2.ex] ...

    Replace [componentName1.ex], [componentName2.ex], etc. with the names of the components you want to find.

    For example:

    path-tracer Button.tsx Modal.tsx

    This will search for the paths of the components named "Button" and "Modal" within the current directory and its subdirectories.

  3. The script will display a progress bar indicating the search progress.

  4. Once the search is complete, the script will write the paths of the components to a file named components_paths.txt. This file will be created on your desktop or in the script's directory, depending on your operating system.

Notes

  • If NO component names and extensions are provided as command-line arguments, an error message will be displayed.
  • The script searches for components recursively in the specified directory and its subdirectories.
  • If a component is found, its path will be displayed next to its name. If not found, "Not found" will be indicated.