Awesome

jsdoc-md

A Node.js CLI and equivalent JS API to analyze source JSDoc and generate documentation under a given heading in a markdown file (such as readme.md).

Installation

To install with npm, run:

npm install jsdoc-md --save-dev

Then, use either the CLI command jsdoc-md or the JS API function jsdocMd to generate documentation.

CLI

Command jsdoc-md

Analyzes JSDoc from source files nested in the current working directory to populate a markdown file documentation section. Source files are excluded via .gitignore files. If the optional peer dependency prettier is installed, the new markdown file contents is Prettier formatted.

It implements the function jsdocMd.

Arguments

Examples

Using npx.

With defaults:

npx jsdoc-md

With arguments:

npx jsdoc-md --source-glob **/*.{mjs,cjs,js} --markdown-path readme.md --target-heading API

Using package scripts.

package.json scripts for a project that also uses eslint and prettier:

{
  "scripts": {
    "docs-update": "jsdoc-md",
    "docs-check": "jsdoc-md -c",
    "eslint": "eslint .",
    "prettier": "prettier -c .",
    "test": "npm run eslint && npm run prettier && npm run docs-check",
    "prepublishOnly": "npm test"
  }
}

Run the prettier script before docs-check in the test script so prettier reports formatting errors instead of jsdoc-md.

Whenever the source JSDoc changes, run the docs-update script:

npm run docs-update

API

function jsdocMd

Analyzes JSDoc from source files to populate a markdown file documentation section. Source files are excluded via .gitignore files. If the optional peer dependency prettier is installed, the new markdown file contents is Prettier formatted.

Returns: Promise<void> — Resolves once the operation is done.

Examples

Ways to import.

import { jsdocMd } from "jsdoc-md";

import jsdocMd from "jsdoc-md/jsdocMd.mjs";

Customizing options.

jsdocMd({
  cwd: "/path/to/project",
  sourceGlob: "index.mjs",
  markdownPath: "README.md",
  targetHeading: "Docs",
}).then(() => {
  console.log("Done!");
});

Caveats

No code inference

Missing JSDoc tags are not inferred by inspecting the code, so be sure to use all the necessary tags.

/**
 * The number 1.
 * @kind constant
 * @name ONE
 * @type {number}
 */
const ONE = 1;

Tag subset

A JSDoc tag subset is supported:

• @desc/@description
• @kind
• @name
• @typedef
• @callback
• @type
• @prop/@property
• @arg/@argument/@param
• @return/@returns
• @emits/@fires
• @see
• @example
• @ignore

Namepath prefixes

Some JSDoc namepath prefixes are not supported:

• module:
• external:

Namepath special characters

JSDoc namepath special characters with surrounding quotes and backslash escapes (e.g. @name a."#b"."\"c") are not supported.

Inline tags

One JSDoc inline tag link syntax is supported for namepath links in JSDoc descriptions and tags with markdown content: [`b` method]{@link A#b}. Use normal markdown syntax for non-namepath links.

Other inline tags such as {@tutorial} are unsupported.

Example content

@example content outside <caption /> (which may also contain markdown) is treated as markdown. This allows multiple code blocks with syntax highlighting and explanatory content such as paragraphs and images. For example:

/**
 * Displays a message in a native popup window.
 * @kind function
 * @name popup
 * @param {string} message Message text.
 * @example <caption>Say `Hello!` to the user.</caption>
 * This usage:
 *
 * ```js
 * popup("Hello!");
 * ```
 *
 * Displays like this on macOS:
 *
 * ![Screenshot](path/to/screenshot.jpg)
 */
const popup = (message) => alert(message);