apidoc is a command-line utility and programmatic library for generating comprehensive RESTful web API documentation directly from comments embedded within source code. It supports a wide array of programming languages by parsing specialized JSDoc-style comments (e.g., `/** ... */` for JavaScript/Java/C#, `""" ... """` for Python) marked with `@api` tags. The current stable version is 1.2.0, released in February 2024, reflecting a consistent, moderate release cadence focused on stability and feature enhancements. Its key differentiators include a language-agnostic parsing engine that understands various comment styles, a flexible plugin architecture for extending functionality (such as integrating API schemas), and robust programmatic integration options for custom build pipelines. The output is static HTML documentation, making it easy to host and integrate into any project.
npm install apidocVerified import paths — ran on the pinned version, not inferred.
Demonstrates programmatic API documentation generation using `createDoc`, illustrating how to specify source/destination paths, control output, and access the parsed documentation data and project information.
Upgrade your Node.js environment to version 16 or higher. Tools like `nvm` or `volta` can help manage multiple Node.js versions.
Upgrade to apidoc v1.0.0 or higher. If upgrading is not immediately possible, try running the CLI with `apidoc -i src/ -o doc/ --debug`.
Ensure you are using apidoc v1.0.2 or newer. If issues persist, consider simplifying `@apiGroup` names to alphanumeric characters and hyphens.
Thoroughly review your `@api` comment syntax against the official apidocjs.com documentation. Use the `dryRun: true` option in programmatic usage or the `--debug` flag in CLI mode to get more detailed parsing output and identify syntax errors.
Install apidoc globally: `npm install -g apidoc` or `yarn global add apidoc`. Verify your npm/yarn global bin directory is correctly set up in your shell's PATH.
Upgrade your Node.js version to 16 or higher. For example, using nvm: `nvm install 16 && nvm use 16`.
Always check if `typeof docResult !== 'boolean'` after calling `createDoc`. If it's `true`, an error occurred. Ensure `silent: false` in your configuration to see console errors, and verify your `src` directory exists and contains valid `@api` comments.
Double-check your `--input` (or `src`) paths and ensure `--exclude` (or `excludeFilters`) options are not overly restrictive. Verify your source files contain correctly formatted `@api` comments. If on an older apidoc version, upgrading to v1.0.0+ resolves a known bundle generation bug.
No dependency data recorded yet.