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

npm-dep-info

v1.4.0

Published

Generates a glimpse of descriptions for your dependencies in the package.json

Downloads

4

Readme

npm-dep-info

Generates a glimpse of descriptions for your dependencies in the package.json

Install

npm install npm-dep-info -g

Example

Have you ever got confused of what your NPM packages do? Sometimes it just can't be told by their names.

Example taken from exorcist's package.json

{
  "name": "exorcist",
  "dependencies": {
    "minimist": "0.0.5",
    "mold-source-map": "~0.3.0",
    "nave": "~0.5.1"
  },
  "devDependencies": {
    "tap": "~0.4.3",
    "browserify": "~3.20.0",
    "through2": "~0.4.0"
  }
}

With npm-dep-info, you get a nice description of these packages:

{
  "dependencies": {
    "minimist": "parse argument options",
    "mold-source-map": "Mold a source map that is almost perfect for you into one that is.",
    "nave": "Virtual Environments for Node"
  },
  "devDependencies": {
    "tap": "A Test-Anything-Protocol library",
    "browserify": "browser-side require() the node way",
    "through2": "A tiny wrapper around Node streams2 Transform to avoid explicit subclassing noise"
  }
}

It can generate a Markdown file for you, too.

And a table output:

dependencies
┌─────────────────┬───────────────────────────────────────────────────────┐
│ name            │ description                                           │
├─────────────────┼───────────────────────────────────────────────────────┤
│ minimist        │ parse argument options                                │
├─────────────────┼───────────────────────────────────────────────────────┤
│ mold-source-map │ Mold a source map that is almost perfect for you into │
│                 │ one that is.                                          │
├─────────────────┼───────────────────────────────────────────────────────┤
│ nave            │ Virtual Environments for Node                         │
└─────────────────┴───────────────────────────────────────────────────────┘
...

Usage

Usage:
  npm-dep-info [OPTIONS] [ARGS]

Options:
  -M, --markdown         Output as Markdown
  -T, --table            Output as table
  -I, --include STRING   Include extra properties from package.json of the
                         dependency (e.g. --include version,homepage)
  -o, --output PATH      Write output to file
  -i, --input PATH       Location of package.json (default ./)

Output a description from the current directory:

npm-dep-info
npm-dep-info -M # markdown
npm-dep-info -T # table

Output to file:

npm-dep-info -o dependencies.json
npm-dep-info > dependencies.json # pipe

Include extra info

npm-dep-info --include version,homepage # split by ","