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

dep-tracer

v1.0.3

Published

This is a tiny tool to find a installed dependency location in your project.

Readme

Dep Tracer

This is a tiny tool to find a installed dependency location in your project.

Imagine you are working in a framework like Next.js or Modern.js, maybe you want to debug into the ts-loader or babel-loader under that framework, and you are using pnpm workspace, it would be hard to find the package location, like ~/my-app/node_modules/.pnpm/[email protected]/node_modules/picocolors. So you can use this little tool to help you, just type dep-tracer picocolors at your project root, or you can be more accurate, dep-tracer next postcss picocolors,

Install

npm i dep-tracer -g
pnpm i dep-tracer -g
yarn add dep-tracer -g

Or use latest and not install locally:

npx dep-tracer foo

Usage

dep-tracer next postcss picocolors  

# output like
Found:
Locations: /my-app/node_modules/.pnpm/[email protected]/node_modules/picocolors
Through: next > postcss > picocolors

Cost: 13ms

Or you can use dt as alias

dt next postcss picocolors

Note

If you are trying to locate a dep from depA > depB > depC > depD > depE > target, if you give it target as only input, it will fail as the dependency chain is too deep.

But you can provide more detail information, like depC target, when it reached dependency depC, it will reset depth 0, so it can continue resolving, and succeed to resolve target.

The more detail you provide, the faster it can run.