Custom Modules for Typedoc
By default, Typedoc (with the
mode="modules" option) will create a Module (née "External Module") for every file with any exported ES6 constructs. This can result in an unmanageable amount of globals, poor discoverability, and difficult navigation. This plugin enables the grouping of these modules by a particular name.
This plugin supports two additional comment tags:
@moduledefinition ModuleNamecan be placed at the top of a file that best represents a "module" for your codebase. This will create a
ModuleNamemodule in the top-level project hierarchy.
@module ModuleNamecan be added to the comment of any other valid exported Typescript declaration (e.g. a class, interface, function, enum etc). These declarations will be moved to any modules specified with
@moduledefinition. Any orphaned modules (e.g. a file that exports a
@module-tagged class and nothing else) are deleted.
Additionally, all exported TS constructs not explicitly tagged with
@module are automatically unwrapped from the default "module" (which is just the file in which it is defined) and placed directly beneath the project. This should be identical to using Typedoc with
test/multiple-ancestor-modules directory for a typical use case for this plugin.
Inspired by the popular typedoc-plugin-external-module-name, but with a slightly different set of requirements. This plugin leverages some improved TypeDoc comment APIs to support spaces within module names.
See the companion theme for an optional, slightly customized version of the default theme with this plugin in mind.
Potential future enhancements:
- Support per-file
@moduletags as well. Individual export
@modules would override any file
- Nested modules with a
@parenttag or something
- Support automatic creation of modules (such that a
@moduledefinitionisn't required for every potential