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

ur

v0.1.0

Published

Analyze a node project for packages that are required but not included in the package.json, or in package.json but not required.

Downloads

5

Readme

ur - unrequired love

ur finds problems with node dependencies. It can find dependencies in your package.json that you never require, or find dependencies you require that you didn't put in your package.json. It ignores relative requires and node built-ins, and uses detective to be smart about finding all requires. It also supports coffee-script files if that is your thing.

Installation

By default ur gives you a binary, so you might want to install it globally.

npm install -g ur

If you just want to use the library, just install it locally

npm install --save ur # put it in your package.json

Usage

Usage: ur [options] [command]

Commands:

  req [path]             find dependencies that are required but not in package.json. defaults to cwd.
  unreq [path]           find dependencies that are in package.json but not required. defaults to cwd.

Options:

  -h, --help     output usage information
  -V, --version  output the version number

API

unrequired(filePath, cb)

Take a file path to a directory containing a package.json file and some javascript files, and return an array of dependencies that are in the package.json but not required.

  • filePath String - a path to a directory with a package.json file and some js files
  • cb Function - cb(err, unrequired) will be called with either an error or null and an array of unrequired dependencies.

For example:

var ur = require('ur')

ur.unrequired(__dirname, function(err, unrequired) {
  console.log('err is', err, 'unrequired deps are', unrequired)
})

required(filePath, cb)

Take a file path to a directory containing a package.json file and some javascript files, and return an array of dependencies that are required in the code but not in the package.json dependencies

  • filePath String - a path to a directory with a package.json file and some js files
  • cb Function - cb(err, required) will be called with either an error or null and an array of required but not in package.json dependencies.

For example:

var ur = require('ur')

ur.required(__dirname, function(err, required) {
  console.log('err is', err, 'required deps are', required)
})

Contributing

Just fork, clone, and pull request. Make sure you run the tests with npm test, and make sure you add tests to any new behavior you add.