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

unused-package

v1.1.2

Published

unused-package is a dependency analysing tool which lets you know which packages are not being used or if package is devDependency but installed as normal dependency

Downloads

390

Readme

unused-package

unused-package is a dependency analysing tool which lets you know which packages are not being used or if package is devDependency but installed as normal dependency

Installation

Using npm

npm install unused-package --save-dev

Using yarn

yarn add --dev unused-package 

Usage

create a file named unused.js in root directory with below code

const check = require("unused-package");

check({ entries: ['entry path to your code'] }).then((res) => {
  console.log(res) // list of packages returned by library
});

Example:
//for react projects
check({ entries: ['src'] }).then((res) => {
  console.log(res)
});

//for next.js projects
check({ entries: ['pages','src','components','next.config.js'] }).then((res) => {
  console.log(res)
});

Note:

  • if your code has mutiple entry paths, you can pass all entry points as array form to entries parameter
  • library returns the list of packages in array format. listed packages maybe not being used in code, or if devDependency is installed as normal dependency.

Include unused.js file in your build script to check for extra packages before every build step in package.json

Example:
//for react projects
"scripts":{
   "build": " node unused.js && react-scripts build",
}
//for next.js projects
"scripts":{
   "build": " node unused.js && next build",
}

OR

create a seperate script to run unused.js file

"scripts":{
  "detect:unused:packages": " node unused.js"
}

Note: Currently package is still in initial phase and if library returns and false positives please feel free to open an issue