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

wtf-dependencies

v1.0.1

Published

**wtf-dependencies** is a CLI tool to trace where (and how deeply) a given dependency is nested in your Node.js project's dependency tree (from package-lock.json). Useful for understanding why a package is present in node_modules.

Readme

WTF-Dependencies version

wtf-dependencies is a CLI tool to trace where (and how deeply) a given dependency is nested in your Node.js project's dependency tree (from package-lock.json). Useful for understanding why a package is present in node_modules.


Install:

  • From npm (recommended):
    • npm install wtf-dependencies
    • or globally: npm install -g wtf-dependencies
  • Or clone: git clone <repo-url> && cd wtf-dependency && npm install
  • (Optional, for local dev): npm link

Usage:

  • After global install, run from any project root (where package-lock.json is):
    • wtf-dependencies <dependency-name>
    • Example: wtf-dependencies lodash

Output Examples:

  • Direct: Dependencies path: lodash
  • Nested: Dependencies path: foo → bar → lodash
  • Not found: No dependencies found in package-lock.json or Usage: wtf-dependencies <dependency-name>

Error Handling:

  • No package-lock.json found: Run from the correct directory.
  • No dependencies found: Run npm install to generate dependencies.
  • No dependency name: Add the name to the command.

Notes:

  • Supports npm v7+ (package-lock v2/v3) and older lockfile formats.
  • Run from your project root, not node_modules.

Contributing:

  • Fork, branch, commit, and open a pull request.
  • For bugs/features, open an issue.

License: ISC. See LICENSE.

Changelog:

  • 1.0.0: Initial release (npm v7+ and legacy support)