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

proon

v1.6.0

Published

A tool to check for unused and unspecified dependencies.

Downloads

17

Readme

proon

A tool to check for unused and unspecified dependencies.

What it does

proon will traverse over the source code in a directory and find all the places in your code where a module is require-d. It then checks the list of require-d modules against the dependency lists in your package.json.

If you have modules which are required in your code and not listed as dependencies in package.json, or vice versa, then it will tell you.

Usage

You can either install the proon binary as a global, or use npx if you're using the latest npm version.

Then run the proon command with an optional directory (defaults to .):

$ proon [dir]
$ npx proon [dir]

Options

  • --reporter - define how the results are output to the console. Available options are default and json.
  • --production - if set to true then proon will only consider modules listed in dependencies (i.e. will ignore devDependencies and optionalDependencies). Additionally will ignore files found in ./test directory.
  • --ignore-binaries - if set to true then proon will not attempt to check if module binaries are used in npm scripts.
  • --ignore - prevent parsing code in particular files or directories. By default anything in .gitignore file is ignored.
  • --include - add additional file patterns to the list of files to be parsed. By default all files matching **/*.js?(x) are parsed. Pass additional globs to include other files.

Important notes

proon only (for now) checks for modules that are require-d in .js files (or .jsx files) or used in npm scripts. If you are using a module in some other way, or in a non-.js file then it may show as unused.

For example, the following cases will not be matched:

  • If a module is used in a non-javascript file - e.g. sass
  • If a module name is dynamically constructed - e.g. require('lo' + 'dash')

Checking in npm scripts is not 100% reliable yet, in part due to a minor bug in npm which doesn't show all binaries for a module.

What about import?

Not yet. Maybe soon.

Related projects