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

man-modules

v0.1.2

Published

Generate man pages for all top-level node_modules

Downloads

21

Readme

man-modules

Generate man pages for all of your node modules

NPM

Installing

npm install man-modules

You can also generate man pages for all globally installed man-modules if installed globally.

Usage


$ man-modules

Or add it for postinstall in your package.json

  "main": "index.js",
  "scripts": {
    "postinstall": "man-modules && node app.js",

Make sure to add the new path to your ~.bashrc after running.


echo "MANPATH=:/home/meandave/Code/man-modules/node_modules/.man; export MANPATH" >> ~/.bashrc'

This will be printed into the terminal after running man-modules.

manpage numbers

The numbers generated for each manpage does not currently mimmick manpage functionality entirely.

On unix systems these stand for:

  1. General commands
  2. System calls
  3. C library functions
  4. Special files (usually devices, those found in /dev) and drivers
  5. File formats and conventions
  6. Games and screensavers
  7. Miscellanea
  8. System administration commands and daemons

Where as here, we are simply incrementing for each readme packaged with the project to ensure no loss of information.

I would like to find a more standard way to handle this. Possibly checking for a bin key in the package.json to signify an executable. Or simple concatting these files together into one big modulename.1 file.

If you have any suggestions for this please open an issue!

Thanks

Much appreciation to @chrisdickinson & @justinabrahms for the inspiration.

LICENSE

MIT