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

docr

v0.0.6

Published

Small javascript to markdown documentation tool

Downloads

11

Readme

docr

Small javascript to markdown documentation tool

usage

npm install -g docr

docr file|pattern [ file|pattern] [--prepend file] [--append file] [--intro]
  pattern    Linux will expand wildcards so remember to escape
             them "\*"
  prepend    can be repeated many times
  append     can be repeated many times
  intro      if the file has an intro (comment at the very
             beginning of the file) it will be used

Documentation will be printed to stdout.

examples

# multiple files
docr index.js lib/xxx.js

# globbing support
docr lib/*

File compatibility

docr is very simple. Do not support prototype or even objects. It's made some modules i have that has recursive require(s).

As you may know, when you have recursive require the easiest way to solve it is to write you module like this.

module.exports = {
    power: power
}

function _private_function() {
    // this function won't be documented because starts with "_"
}

/**
 * Give me some power!
 *
 * @param {Number} a
 * @param {Number} b
 * @return {Number}
 */
function power(a, b) {
    return Math.power(a, b);
}

docr will generate documentation for any function that has a doc-block. To be coherent function name must be the same as exports.

jsDoc support.

  • description
  • @param
  • @note
  • @return
  • @example (partial support)

new

  • @name String

    Force the function name in the documentation.

projects that use docr