TypeDoc reads webpack/types.d.ts
TypeDoc is pointed at webpack’s
types.d.ts entry point. It parses every exported type, interface, class, and accessor into a structured reflection tree.Custom plugins process the output
Three plugins run during the TypeDoc build:
typedoc-plugin-markdown— renders the reflection tree as Markdown files.plugins/processor.mjs— mergesexport=namespaces into their parents, converts accessors to properties, and emits atype-map.jsonfile that maps every fully-qualified type name to its final HTML URL.plugins/theme/index.mjs— registers a customdoc-kittheme that extends the Markdown theme with custom helpers and partials, and enforcespropertiesFormat: table.
@node-core/doc-kit converts Markdown to HTML
The
doc-kit generate command reads the Markdown pages written by TypeDoc and the type-map.json produced by the processor plugin, then emits static HTML into the out/ directory.Version pinning with HEAD_COMMIT
The fileHEAD_COMMIT contains a single full commit SHA that identifies the exact webpack/webpack commit used to generate the current documentation:
deploy.yml, ci.yml, and sync.yml) reads this file and passes the SHA as the ref when checking out the webpack/webpack repository. This means the documentation always corresponds to a known, reproducible state of webpack — never an uncontrolled main tip.
The sync.yml workflow updates HEAD_COMMIT automatically when the webpack main branch moves forward. See the Webpack version sync page for details.
Explore further
TypeDoc pipeline
How
generate-md.mjs bootstraps TypeDoc, which options are used, and what each plugin contributes.Webpack version sync
How the daily
sync.yml workflow keeps the pinned webpack commit up to date.