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

npm-what

v1.0.0

Published

πŸ” are you really using node modules properly?

Downloads

12

Readme

npm-what

πŸ” are you really using node modules properly?

Npm Version Coverage Status Dependency Status devDependency Status npm npm

Installation

npm install npm-what -g

Usage

Usage: npm-what [options]

Commands:
  -h, --help, help             Output usage information
  -v, --version, version       Output the version number

Options:
  -d, --directory [path]       The path of the project you want to check (default directory is process.cwd())

Key

| Emoji | Explanation | What should you do | |----------|:-------------:|------:| | πŸ–• | you aren't even referencing this module | install this globally not explicitly in the project | | πŸ™„ | this is less than a hundred lines of code | grab the parts you need, ditch the package | | πŸ”¨ | needs some work, but referenced enough times to mandate use | you should contribute to this project | | πŸ‘ | congratulations πŸ‘| Cool you use modules... |

Example

npm-what running against itself

$ npm-what

βœ” Parsed 7 modules

> Project
| LOC  | Modules Required |
| ---- | ---------------- |
| 6879 | 7                |

> Modules Required
| Module                | LOC   | Ocurrences | Verdict |
| --------------------- | ----- | ---------- | ------- |
| cloc@^2.3.2           | 12621 | 0          | πŸ‘      |
| depcheck@^0.6.8       | 2295  | 1          | πŸ‘      |
| markdown-table@^1.1.1 | 565   | 1          | πŸ‘      |
| ora@^1.3.0            | 411   | 1          | πŸ”¨      |
| eslint@^4.13.1        | 63751 | 1          | πŸ‘      |
| tap@^11.0.0           | 3708  | 1          | πŸ‘      |
| tape@^4.8.0           | 3707  | 2          | πŸ‘      |

> if you see modules that are not in your package.json running `npm update` should resolve your project tree

TLDR;

This module finds the amount of code that your project consists of, then it finds the amount of code used by all of your dependencies and gives you a grade based on how well you are using that dependency