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

dependency-lint

v7.1.0

Published

Lints package.json dependencies and devDependencies

Downloads

14,513

Readme

dependency-lint

Build Status Dependency Status NPM Version

Lints your NPM dependencies and devDependencies reporting which node modules are

  • missing and should be added to your dependencies or devDependencies
  • unused and should be removed from your dependencies or devDependencies
  • mislabeled and should be moved from dependencies to devDependencies or vice versa

Installation

Supported on Node.js versions 12, 14, 16

$ npm install dependency-lint

Usage

$ dependency-lint

To automatically remove unused dependencies and move mislabeled dependencies:

$ dependency-lint --auto-correct

How it works

dependency-lint compares the node modules listed in your package.json and the node modules it determines are used. A node module is used if:

  • it is required in a javascript file (or a file that transpiles to javascript)
  • one of its executables is used in a script in your package.json or in a shell script

Since this does not cover all the possible ways that a node module can be used, dependency-lint can be configured to ignore specific errors. Please create an issue anytime you need to use this, so we can discuss new ways to determine if and how a node module is used.

Configuration

Please see here for an explanation of all the options. Custom configuration should be placed at dependency-lint.yml in your project directory. You can create a configuration file by running

dependency-lint --generate-config

Any options not set in your configuration file will be given there default value.

Formatters

Three formatters are available and can be switched between with the --format option

dependency-lint --format <format>
  • minimal (default) - prints only the modules with errors
  • summary - prints all modules
  • json - prints JSON of the form {dependencies, devDependencies} where each is array of objects with the keys
    • name - name of the module
    • files - list of the files that require the module or execute the module
    • scripts - list of scripts in your package.json that execute the module
    • error - null or one of the following strings: "missing", "should be dependency", "should be dev dependency", "unused"
    • errorIgnored - if dependency lint has been configured to ignore this error.