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 🙏

© 2024 – Pkg Stats / Ryan Hefner

whats-in-my-deps

v0.8.4

Published

a cli tool that takes a wiff on your node_modules and spits some stats about it

Downloads

6

Readme

What's in my deps? statistics for your installed modules.

This is a simple CLI tool that takes a whiff of your node_modules and spits out some statistics about them.

Coverage Status

usage:

npx whats-in-my-deps

Expect output that ends like so:


 Summary:
   total:      41
   redundant:  9        (just the extra dups)
   fake:       0        (tests, example or boilerplate)
   Errored:    0

 Stats:
   CJS:        24
   ESM:        15
   DUAL:       2
   TYPES:      0
   misc.:      0        (i.e .node, .json)

By default, it looks for node_modules in your current work directory. However, you can pass it a path as an argument.

npx stat-my-deps ~/workspace/my-project

What are these statistics?

Summary

  • total - the number of package.json files the glob found in the node_modules directory.
  • redundant - the number of duplications - the count of redundant coppies of existing packages. e.g. if a a package was found 4 times - then 3 of them are duplications. This treats different versions of the same package also as duplicates.
  • fake - package.json that were found in the node_modules directory, but do not represent a real package. Either because they were transpiled to dist, or they are a part of a boilerplate the package uses, or a part of its tests. (this stat is pending deprecation ever since the glob that finds package.json files was refined).
  • Errored - packages that the code failed to analyse and identify what they are.

Stats

  • CJS - the shipped code in the package was identified as commonJS. (it could be transpiled from ESM, but the actual distribution is CJS).
  • ESM - the shipped code in the package was identified as ES-Modules.
  • Dual - the package includes an exports clause. (this is a naive assumption that may be refined in a PR)
  • Types - the package is identified as a types package.
  • misc. - the package does not ship JS code, but .node, .json, local-arch binaries or other miscellaneous files.