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

depchecka

v1.0.2

Published

Simple node.js script for listing unused dependencies that are in your package.json.

Downloads

5

Readme

depchecka

A simple node.js script for finding unused dependencies that are in your package.json.

depchecka will load the list of dependencies from the package.json file found in the current working directory and then recursively traverse the directory tree starting at the specified directory path, processing all javascript files (.js, .jsx, .ts, .tsx, .astro, .svelte), looking for use of those dependencies. The list of unused dependencies is shown on completion.

NOTE: Some frameworks may include dependencies in package.json that may be listed as unused by this tool. Also, if you have installed dev dependencies as regular dependencies these may also be listed as unused.

Usage

From the root of your project (where the main package.json lives) run:

npx depchecka ./path/to/entry-point

./path/to/entry-point should be your source directory or where you want depchecka to start recursively looking for dependencies used (defaults to ./src).

Example

➜ npx depchecka ./src
Processed 1288 files in 496ms

Unused deps: {
  '@material-ui/lab': '4.0.0-alpha.60',
  'arrow-keys-react': '1.0.6',
  'date-fns': '2.16.1',
  'intl-messageformat-parser': '4.1.1',
  'react-fast-compare': '3.2.0',
  'react-input-autosize': '2.2.2',
  'react-intl-context': '1.0.3',
  'react-transition-group': '4.4.1',
  stylis: '4.1.0'
}

Pre-requisites

depchecka requires node >= 18.11.0 in order to run