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

myrtlelime-depcheck

v1.0.3

Published

A tool for checking for unused dependencies

Downloads

256

Readme

Depcheck

depcheck looks through the files in your project to either:

  • With depcheck: find packages that are listed in package.json that are no longer used
  • With localcheck: find files that are not referenced by any other Javascript file (e.g., orphaned in a refactor)

Usage

To use depcheck or localcheck, you need to create a depcheck.json file, which has the following format:

  • files: array of globs whose require/import statements you want to check

  • filesToCheck: the package.json or other files you'd like to check. This can either be an array of files, or a hash in the format of:

    {
      "vendorPackages.json": "fullPath",
      "packages.json": "packages",
    }

    packages means we want to make sure the package itself is defined (e.g., react-bootstrap), while fullPath means we want the full required string to be present (react-bootstrap/lib/Modal).

    For files named package.json, it'll look in dependencies and devDependencies. For all other files, it will assume the file is an array of packages, and just look in the top-level array.

  • ignorePackages is a list of packages that you'd like to be ignored even if it seems like they're unused. These are most often used for linters, Babel transforms, and other implicit dependencies.

Once you have a depcheck.json, simply run it using:

depcheck depcheck.json

Sample depcheck.json

{
  "files": [
    "{gulpfile.js,build/**/*.js}",
    "client/{assets,js,templates}/**/*.{scss,js,coffee}",
    "server/{{app,scripts}/**/*.js,app.js}",
    "test/**/*.js"
  ],
  "filesToCheck": ["package.json"],
  "ignorePackages": [
    "babel-core",
    "babel-eslint",
    "babel-loader",
    "babel-preset-react",
    "babel-preset-es2015",
    "babel-plugin-transform-class-properties",
    "bluebird",
    "eslint",
    "eslint-config-airbnb",
    "eslint-config-airbnb-base",
    "eslint-plugin-flowtype",
    "eslint-plugin-import",
    "eslint-plugin-jsx-a11y",
    "eslint-plugin-react",
    "flow-bin",
    "json-loader",
    "minifyify",
    "history",
    "mysql",
    "mocha"
  ]
}