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

cleanup-deps

v1.1.0

Published

Easy detection of useless dependencies in your package.json file

Downloads

4

Readme

cleanup-deps

Easy detection of useless dependencies in your package.json file.

How to use

npx cleanup-deps@latest

inside your project root directory.

cli options

| Option | value | Default | Description | |----------------|----------|---------|------------------------------------------------------| | --path | <path> | pwd | path to directory contains your package.json file. | | --config | <path> | pwd | path to config file |

Configuration

You can create config file to customize the behavior of the tool.

npx cleanup-deps@latest --config ./config.cleanup-deps.mjs

mjs is important. Only ESM modules are supported.

Example of config file:

// config.cleanup-deps.mjs
import { createConfig, declareValidation } from './index.js';

export default createConfig({
  packageJsonPath: '..',
  validateFn: declareValidation({
    'yargs': {
      minimalNodeVersion: '0.0.0',
      message: 'test',
      validUntil: new Date(),
    }
  })
})

config API

createConfig

Wrapper for config object for better IDE support. Example of usage you can see above. Arguments:

  • packageJsonPath - path to package.json file. Default: process.cwd()
  • validateFn - function that will be called for each dependency. Please see createValidationFn for more details.
declareValidation

Helper function to declare validation rules for specific package. Example of usage you can see above. Arguments:

  • key of the object - package name
  • value:
    • minimalNodeVersion - minimal node version for which package is deprecated.
    • message - message that will be shown if package is deprecated.
    • validUntil [Optional] - date until package is valid. If date is expired, package will be marked as deprecated.
createValidateFn

Helper function to create validate function for specific package. Should return validDep or invalidDep. Example of usage you can see in declareValidation file

mergeValidateFn

Helper function to merge validate functions.

Tips

How to hide specific package from the report

You can use --config option to declare config file with validUntil for specific package. For example:

// config.cleanup-deps.mjs
import { createConfig, declareValidation } from './index.js';

export default createConfig({
  packageJsonPath: '..',
  validateFn: declareValidation({
    'object.assign': {
      minimalNodeVersion: '0.0.0',
      message: 'test',
      validUntil: new Date('2030-01-01'),
    }
  })
})

After '2030-01-01' date, the package object.assign will be shown in the report. Before that the package will be undeprecated dep.

Limitations

  • Only dependencies and devDependencies sections are supported.
  • Only node runtime are supported. The browser runtime will be supported in the future.
  • We have a small list of packages in our deprecation list.