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 🙏

© 2026 – Pkg Stats / Ryan Hefner

@mseeley/jsdoc-to-markdown

v0.1.1

Published

Convenience batch-operation wrapper around jsdoc-to-markdown

Readme

This is a package created for personal use. It wraps the jsdoc-to-markdown package with platform-agnostic batch handling and concurrency.

The package is written in a platform agnostic way yet has only been tested on macOS. Testing feedback is welcome.

Simplifying assumptions:

  • There should be a reusable external configuration file.
  • The name of the JavaScript file becomes the name of the Markdown file.
  • Each JavaScript file has a single semantic purpose.
  • Vanilla Markdown output is good enough.

Installation

npm install -D mseeley@jsdoc-to-markdown

Configuration

You can use different ways to configure it:

  • See cosmiconfig for more details on what formats are supported.
  • Or, pass a configuration file using the --config or -c flag

Example ms-jsdoc2md.config.js:

module.exports = {
  // These are the files from which to extract JSDoc comments. This is a glob
  // expression parsed by https://www.npmjs.com/package/glob-promise. The
  // pattern below will examine all JavaScript files in the `lib/` directory
  // which do not include `.spec` in their filename.
  inputPattern: "lib/**/!(*.spec).js",

  // The directory to store the generated markdown docs. It can be an absolute
  // path or resolve relative to `process.cwd()`.
  outputDirectory: "docs/",

  // Optional, maximum number of threads to spawn. Defaults to the number of
  // physical CPUs detected.
  concurrency: Number,

  // Optional, the extension of the files parsed for JSDoc comments. Defaults to
  // ".js".
  inputFileExtension: String,

  // Optional, verbose CLI output. Defaults to false.
  verbose: Boolean
};

Usage

The package intentionally fails immediately when an error is encountered. The package doesn't expose an API; best to use it as an NPM script:

Add the script to your package.json.

"scripts": {
  "doc": "ms-jsdoc2md"
}

Invoke it from the command line:

npm run doc

Contributing

Contributions are welcome. Please see ensure that your code and commit message pass linting requirements. See the scripts member of this repo's package.json and husky.config.js for more information.