It is distributed as a JSDoc3 template. Running JSDoc with this as the template should result in a TypeScript Definition File.
You can install this module from npm:
$> npm install tsd-jsdoc
To use this module, simply specify it as the template for your normal JSDoc generation.
For example, from the command-line you can do:
$> jsdoc -t node_modules/tsd-jsdoc/dist -r .
Or add this to your JSON configuration:
This library provides very little validation beyond what JSDoc provides. Meaning if you have invalid JSDoc comments, this will likely output an invalid TypeScript Definition File.
Additionally there are things that JSDoc allows, that TypeScript does not. This library tries to make these differences transparent, and translate from one to the other when necessary. It can't handle anything though, and you can generate invalid Typescript even if your JSDoc is valid.
Tags with no support
Tags that describe the code, but support is not implemented are:
@default- No TS equivalent
@deprecated- No TS equivalent (issue)
@event- No TS equivalent
@exports- Everything is exported
@external- Not sure what behavior would be expected
@fires- No TS equivalent
@listens- No TS equivalent
@override- No TS equivalent (issue)
@throws- No TS equivalent
Tags that are just metadata and don't actually describe the code are ignored. These are:
All other JSDoc tags should work fine.
Supported ClosureCompiler Tags
ClosureCompiler has a couple tags beyond the built-in JSDoc tags that can improve your TypeScript output. Here is a complete list of the tags from CC that are supported in this template:
@template- For generics
Extended support for TS features
JSDoc doesn't have a way to express all the features of typescript so we treat some syntax as special case to create better Typescript.
Class<T>- If we encounter a type that is
Class<T>we will treat it as
typeof T. See jsdoc3/jsdoc#1349