npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2024 – Pkg Stats / Ryan Hefner

@just-boris/typedoc

v0.15.0-1

Published

Create api documentation for TypeScript projects.

Downloads

5

Readme

TypeDoc

About this fork

This fork exists to have a version with latest Typescript support while it is not yet released in the main project: https://github.com/TypeStrong/typedoc/issues/1015

Documentation generator for TypeScript projects.

Build Status NPM Version Chat on Gitter

Installation

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 typedoc.

$ npm install typedoc --global
$ typedoc

Usage

Shell

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/

Important note

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 mode argument in order to change the behaviour of TypeDoc.

Arguments

For a complete list of the command line arguments run typedoc --help or read here.

  • --out <path/to/documentation/> Specifies the location the documentation should be written to.
  • --mode <file|modules> Specifies the output mode the project is used to be compiled with.
  • --options Specify a js option file that should be loaded. If not specified TypeDoc will look for 'typedoc.js' in the current directory.
  • --json <path/to/output.json> Specifies the location and file name a json file describing the project is written to. When specified no documentation will be generated.
  • --ignoreCompilerErrors Should TypeDoc still generate documentation pages even after the compiler has returned errors?

Source file handling

  • --exclude <pattern> Exclude files by the given pattern when a path is provided as source. Supports standard minimatch patterns (see #170)
  • --includeDeclarations Turn on parsing of .d.ts declaration files.
  • --externalPattern <pattern> Define a pattern for files that should be considered being external.
  • --excludeExternals Prevent externally resolved TypeScript files from being documented.
  • --excludeNotExported Prevent symbols that are not exported from being documented.
  • --excludePrivate Prevent private members from being included in the generated documentation.
  • --excludeProtected Prevent protected members from being included in the generated documentation.

TypeScript compiler

  • --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"
  • --tsconfig <path/to/tsconfig.json> Specify a typescript config file that should be loaded. If not specified TypeDoc will look for 'tsconfig.json' in the current directory.

Theming

  • --theme <default|minimal|path/to/theme> 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.
  • --readme <path/to/readme|none> Path to the readme file that should be displayed on the index page. Pass none to disable the index page and start the documentation on the globals page.
  • --plugin Specify the npm plugins that should be loaded. Omit to load all installed plugins, set to 'none' to load no plugins.
  • --hideGenerator Do not print the TypeDoc link at the end of the page.
  • --gaID Set the Google Analytics tracking ID and activate tracking code.
  • --gaSite <site> Set the site name for Google Analytics. Defaults to auto
  • --entryPoint <fully.qualified.name> Specifies the fully qualified name of the root symbol. Defaults to global namespace.
  • --gitRevision <revision|branch> Use specified revision or branch instead of the last revision for linking to GitHub source files.

Content

  • --includes <path/to/includes> Specifies the location to look for included documents. One may use [[include:FILENAME]] in comments to include documents from this location.

  • --media <path/to/media> 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 media://FILENAME in comments.

Miscellaneous

  • --version Display the version number of TypeDoc.
  • --help Display all TypeDoc options.

Webpack

There is a plugin available to run TypeDoc with Webpack created by Microsoft. You can find it on NPM: https://www.npmjs.com/package/typedoc-webpack-plugin

Gulp

There is a plugin available to run TypeDoc with Gulp created by Rogier Schouten. You can find it on NPM: https://www.npmjs.com/package/gulp-typedoc/

Grunt

There is a plugin available to run TypeDoc with Grunt created by Bart van der Schoor. You can find it on NPM: https://www.npmjs.com/package/grunt-typedoc

Plugins

A list of all published Typedoc plugins can be found on NPM: https://www.npmjs.com/search?q=keywords:typedocplugin

Advanced guides and docs

Visit our homepage for advanced guides and an extensive API documentation: https://typedoc.org

Contributing

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: https://github.com/TypeStrong/typedoc

For more information, read the contribution guide.

License

Copyright (c) 2015 Sebastian Lenz. Copyright (c) 2016-2018 TypeDoc Contributors. Licensed under the Apache License 2.0.