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

@itsjamie/typedoc

v0.21.9

Published

Create api documentation for TypeScript projects.

Downloads

3

Readme

TypeDoc

Documentation generator for TypeScript projects.

CI NPM Version

Documentation

For more detailed documentation, the changelog, and TypeDoc documentation rendered with TypeDoc, see https://typedoc.org.

Installation

TypeDoc runs on Node.js and is available as a NPM package.

npm install typedoc --save-dev

Usage

To generate documentation TypeDoc needs to know your project entry point, and TypeScript compiler options. It will automatically try to find your tsconfig.json file, so you can just specify the entry point of your library:

typedoc src/index.ts

If you have multiple entry points, specify each of them. If you specify a directory, TypeDoc will treat each file contained within it as an entry point.

typedoc package1/index.ts package2/index.ts

Monorepos / Workspaces

If your codebase is comprised of one or more npm packages, you can pass the paths to these packages and TypeDoc will attempt to determine entry points based on package.json's main property (with default value index.js) and if it wasn't found, based on types property. If any of the packages given are the root of an npm Workspace or a Yarn Workspace TypeDoc will find all the workspaces defined in the package.json. This mode requires sourcemaps in your JS entry points, in order to find the TS entry points. Supports wildcard paths in the same fashion as those found in npm or Yarn workspaces.

Single npm module

typedoc --packages .

Monorepo with npm/Yarn workspace at the root

typedoc --packages .

Monorepo with manually specified sub-packages to document

This can be useful if you do not want all your workspaces to be processed. Accepts the same paths as would go in the package.json's workspaces

# Note the single quotes prevent shell wildcard expansion, allowing typedoc to do the expansion
typedoc --packages a-package --packages 'some-more-packages/*' --packages 'some-other-packages/*'

Arguments

For a complete list of the command line arguments run typedoc --help or visit our website.

  • --out <path/to/documentation/> Specifies the location the documentation should be written to. Defaults to ./docs
  • --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.
  • --options Specify a json option file that should be loaded. If not specified TypeDoc will look for 'typedoc.json' in the current directory.
  • --packages <path/to/package/> Specify one or more sub packages, or the root of a monorepo with workspaces. Supports wildcard paths in the same fashion as those found in npm or Yarn workspaces.
  • --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.

Source file handling

  • --exclude <pattern> Exclude files by the given pattern when a path is provided as source. Supports standard minimatch patterns.
  • --excludeNotDocumented Only document items which have a doc comment. This option is useful, if you want to document only small part of your symbols and do not show the remaining ones in the documentation.

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.

Miscellaneous

  • --listInvalidSymbolLinks Display the list of links that don't point to actual code symbols.
  • --version Display the version number of TypeDoc.
  • --help Display all TypeDoc options.

Contributing

This project is maintained by a community of developers. Contributions are welcome and appreciated. You can find TypeDoc on GitHub; feel free to open an issue or create a pull request: https://github.com/TypeStrong/typedoc

For more information, read the contribution guide.

License

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