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

package-dependency-stats

v1.0.0

Published

get reigstry stats of all package.json dependencies

Downloads

7

Readme

package-dependency-stats

stable

Gets the npm reigstry stats for all the dependencies in a package.json object. Also see gh-repo-dependencies.

Install

npm install package-dependency-stats --save

Example

var packageStats = require('package-dependency-stats')
var readPackage = require('read-closest-package')

readPackage(function (err, data) {
  if (err) throw err
  packageStats(data, {
    filter: function (pkg) {
      return pkg.list === 'dependencies'
    }
  }, function (err, deps) {
    if (err) throw err

    // print dependency name and registry description
    deps = deps.map(function (d) {
      return d.name + ': ' + d.stats.description
    })
    console.log(deps.join('\n'))
  })
})

Usage

NPM

packageDepStats(packageJson, [opt], [cb])

Fetches npm registry stats from the dependencies in packageJson (an object).

Options:

  • filter (Function) optionally filter the dependencies before querying npm registry

For example, filter could look like this to avoid querying registry stats of devDependencies.

function filterDeps (package) {
  return package.list === 'dependencies'
}

The callback takes the form (err, data), where data is a flat array of dependencies gleaned from dependencies, devDependencies, peerDependencies, optionalDependencies (in that order) unless otherwise filtered.

Each item has the following data:

{
  name: 'inherits',     // name as it appears in package.json
  version: '^2.0.1',    // version range from package.json
  list: 'dependencies', // type of dependency
  stats: { ... }        // registry stats
  error: Error          // Error object if there was a problem
}

If stats could not be retrieved for that package, it will be null and error will be populated with the Error object. Otherwise error will not be defined.

The stats are fetched using npm-stats.

Note: packageJson can be a simple object like so:

{
  dependencies: { ... },
  devDependencies: { ... }
}

See Also

License

MIT, see LICENSE.md for details.