Documentation generator for TypeScript projects.
TypeDoc runs on Node.js and is available as an NPM package. You can install TypeDoc in your project's directory as usual:
$ npm install typedoc --save-dev
Like the TypeScript compiler, TypeDoc comes with a binary that can be called from anywhere
if you install TypeDoc as a global module. The name of the executable is
$ npm install typedoc --global $ typedoc
TypeDoc accepts most of the command line arguments that the TypeScript compiler accepts. One major difference is the fact that one may pass an entire directory instead of individual files to the documentation generator. So in order to create a documentation for an entire project you simply type:
$ typedoc --out path/to/documentation/ path/to/typescript/project/
Starting with version 0.2, TypeDoc no longer can predict whether files should be treated as modules
or whether the project should be compiled into one big namespace. You must specify the
in order to change the behaviour of TypeDoc.
Specifies the location the documentation should be written to.
Specifies the output mode the project is used to be compiled with.
Specify a js option file that should be loaded. If not specified TypeDoc will look for 'typedoc.js' in the current directory.
Specifies the location and file name a json file describing the project is written to. When specified no documentation will be generated.
Should TypeDoc still generate documentation pages even after the compiler has returned errors?
Source file handling
Exclude files by the given pattern when a path is provided as source. Supports standard minimatch patterns (see #170)
Turn on parsing of .d.ts declaration files.
Define a pattern for files that should be considered being external.
Prevent externally resolved TypeScript files from being documented.
Prevent private members from being included in the generated documentation.
Prevent protected members from being included in the generated documentation.
--module <commonjs, amd, system or umd>
Specify module code generation: "commonjs", "amd", "system" or "umd".
--target <ES3, ES5, or ES6>
Specify ECMAScript target version: "ES3" (default), "ES5" or "ES6"
Specify the path to the theme that should be used.
--name <Documentation title>
Set the name of the project that will be used in the header of the template.
Path to the readme file that should be displayed on the index page. Pass
noneto disable the index page and start the documentation on the globals page.
Specify the npm plugins that should be loaded. Omit to load all installed plugins, set to 'none' to load no plugins.
Do not print the TypeDoc link at the end of the page.
Set the Google Analytics tracking ID and activate tracking code.
Set the site name for Google Analytics. Defaults to
Specifies the fully qualified name of the root symbol. Defaults to global namespace.
Use specified revision or branch instead of the last revision for linking to GitHub source files.
Specifies the location to look for included documents. One may use
[[include:FILENAME]]in comments to include documents from this location.
Specifies the location with media files that should be copied to the output directory. In order to create a link to media files use the pattern
Display the version number of TypeDoc.
Display all TypeDoc options.
There is a plugin available to run TypeDoc with Webpack created by Microsoft. You can find it on NPM:
There is a plugin available to run TypeDoc with Gulp created by Rogier Schouten. You can find it on NPM:
There is a plugin available to run TypeDoc with Grunt created by Bart van der Schoor. You can find it on NPM:
- External Module Name - Set the name of TypeDoc external modules
- Sourcefile URL - Set custom source file URL links
Internal/External Module - Explicitly mark modules as
Single Line Tags - Process certain
@tagsas single lines
Advanced guides and docs
Visit our homepage for advanced guides and an extensive API documentation:
This project is maintained by a community of developers. Contributions are welcome and appreciated.
You can find TypeDoc on GitHub; feel free to start an issue or create a pull requests: