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

nd

v1.2.0

Published

a documentation viewer for node

Downloads

80

Readme

nd

a documentation viewer for npm

nd is a documentation viewer for npm packages. Similar to mad(1), it displays markdown documents in your terminal. Dissimilarly to mad, nd is written in javascript, and reads documentation out of npm module directories, not out of its own repository of pages.

By writing this software in javascript, we benefit from the existing require() circuitry. This means that there is a large volume of useful documentation available, despite the fact that very few packages have a doc or docs folder. Nearly every package at least has a README.md; nd will read this.

If a doc or docs directory is present, or if there is a docs directory specified in the package.json of some module, documentation will be loaded out of these directories.

For example, if we type

$ nd npm cli

We will get npm/doc/cli/index.md. So, if additional arguments (besides the module name) are provided, we try to find a file which is more specific: we'll look for module/arg1/arg2/index.md, module/arg1/arg2/arg2.md, and module/arg1/arg2.md. This allows us to be flexible about the organization of documentation within modules.

Usage

To install:

$ sudo npm install -g nd

Note that you may not need sudo if you installed node via a virtual environment manager such as nvm.

To use:

$ nd modulename

nd searches for modules from within the current directory. If it can't find the module you're looking for in the current directory, it will search for modules installed globally with npm -g.

You can also type simply

$ nd

to get a list of modules in the current directory.. You can run nd with the relative path to a markdown file as an argument and nd will read it, or you can pipe it some stuff:

$ nd README.md
$ curl https://github.com/russfrank/nd/raw/master/README.md | nd

nd can also grab core docs, though, I should note that it always takes them straight out of master, which might not be what you want:

$ nd node child_process

You can also just straight up give it urls, it'll figure that shit out.

$ nd https://raw.github.com/joyent/node/master/doc/api/child_process.markdown

Also, it works on Windows, since everybody knows that Windows users love to read docs in their terminal:

Future

More ideas:

  1. Pydoc like web server
  2. Docco view of source files (markdown comments on left, source on right) in terminal
  3. picture-tube for images
  4. command line completion

License

MIT.