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

dead-package-finder

v2.0.0

Published

Find all modules listed in package.json that aren't actually used by your code

Downloads

64

Readme

js-standard-style Build Status Coverage Status

dead-package-finder

Inherit a large project and not sure if the package.json lists things that are actually used in your software? Got failing installs due to really out-of-date packages that you might not need anymore? Get lazy with development and forget to remove packages that you don't use anymore?

This tool is for you!

This walks all the javascript files in a specified directory and uses esprima to find all the require statements in them and matches them up against the packages you've declared a dependency on. If you have a declared dependency that you're not requiring, it'll tell you that so you can take the appropriate action.

nodejs only!

This uses a bunch of ES6 features and so will only work in nodejs 4.0.0 and higher. But you're like using the latest version, right?

If you need a version compatible back to iojs 2.2.0 or later? You can use @1.1.2 — but beware that sometimes verbose will emit a Set and sometimes an Array. Node 4 includes a version of v8 that properly implements Array#from allowing the Set to be easily re-cast as an Array when emitted

Usage

npm install dead-package-finder
./dead-package-finder [options]

Options

Options:
    -h, --help                     print usage information
    -v, --version                  show version info and exit
    -i, --ignore-folder            a list of folders to ignore. node_modules
                                   will ALWAYS be ignored
    -r, --project-root             the path to the directory containing the
                                   package.json file
    -d, --ignore-dev-dependencies  ignore any packages listed in devDependencies
    --verbose                      print out way too much info to even be useful

API

See dead-package-finder.cli.js for examples on how to use this programatically.

License

© 2015 Todd Kennedy, Apache 2.0 license