require-package-documentation

Require a top-level @packageDocumentation comment in modules that export API.

Targeted pattern scope

This rule checks source files containing module exports (export ..., export default, export *, TypeScript export assignments).

What this rule reports

This rule reports modules that export API but do not include a top-level TypeDoc package/module documentation comment.

Why this rule exists

Without package-level docs, generated TypeDoc module pages often lack context about API purpose, usage boundaries, or design intent.

❌ Incorrect

export function parseValue(value: string): number {
    return Number.parseInt(value, 10);
}

✅ Correct

/**
 * @packageDocumentation
 */

export function parseValue(value: string): number {
    return Number.parseInt(value, 10);
}

Behavior and migration notes

Autofix inserts a minimal package documentation block at the top of the file.

ESLint flat config example

import typedocPlugin from "eslint-plugin-typedoc";

export default [
    {
        plugins: { typedoc: typedocPlugin },
        rules: {
            "typedoc/require-package-documentation": "error",
        },
    },
];

When not to use it

Disable this rule for private/internal code where module-level docs are intentionally omitted.

Package documentation

TypeDoc package documentation:

• TypeDoc @packageDocumentation tag

Further reading

Rule catalog ID: R013

• TypeDoc comments and tags

Adoption resources

• Pair with require-exported-doc-comment for complete module + symbol coverage.