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

hmdoc

v0.3.1

Published

A command line utility to generate source code documentation.

Downloads

1

Readme

hmdoc

Simple documentation generator for JavaScript. Based slightly on JavaDoc, but it is much simpler and uses HM type signatures rather than bloated parameter annotations.

Usage

Clone this repo and then run npm install -g in the repo root to install the hmdoc command globally on your system.

Usage:

hmdoc "Name of Project" path/to/src

or

hmdoc "Name of Project" file.js

Example

Example of source code that can be processed

/**
 *  Module Name
 *  written by Author Name
 *  on MM/DD/YYYY
 *
 *  Description of the module.
 */

/**
 *  foo :: string -> string -> string -> ()
 *
 *  A function that doesn't do anything.
 */
function foo(a,b,c) {}

/**
 *  arrow :: Monad m => (a -> m b) -> (b -> m c) -> a -> m c
 *
 *  Kleisi composition of JavaScript "monads"
 */
function arrow(a, b) {
	return function(x) {
		return a(x).bind(b);
	}
}

It works just as well with OO style code using ES6 classes, as long as you follow the rule one module = one file = one class

/**
 *  Animal
 *  written by Author Name
 *  on MM/DD/YYYY
 *
 *  The beginnings of a classic subtyping example
 */
class Animal {
  /**
   *  new :: string -> Animal
   *
   *  Constructs a new Animal
   */
  constructor(name) {
    this.name = name;
  }
  
  /**
   *  eat :: Animal -> string -> ()
   *
   *  Make the animal eat some food.
   */
  eat(food) { }
}

Note

This project would currently be in "alpha" state and likely has severe bugs. I'm currently using it for my own purposes and it is working fine, but it does not have any error messages currently and expects comments to be in exactly the format that I have used them (actually it will handle some parts of the comments in a more user-friendly way, but not the entire comment yet).

This program does not parse JavaScript/ES. It only looks for /** */ comments in the source code and processes the text within them. The program does not have any access to the AST of your code to match it against the comments or perform any instrumentation against your code. I might add something like this at a later time, but I want to keep this thing as simple as possible.

To see an example of the documentation produced, you can run this program on itself. Running npm install should do this as well, but npm install -g doesn't seem to run my install script on my system (maybe it will on yours).

Yes I'm abusing HM type signatures by using them on non-curried functions. Whatever...