-
Notifications
You must be signed in to change notification settings - Fork 152
How to document TypeScript
Babel started to support TypeScript from version 7.
Since most modules are at pre-release stage as of this writing, I had to insert latest version numbers by hand. Update version numbers accordingly. After pre release stage, there would be no need to put version numbers.
Either run the following:
npm install -save-dev typescript [email protected] @babel/[email protected] @babel/[email protected] @babel/[email protected] @babel/[email protected] @babel/[email protected] @babel/[email protected] [email protected] jsdoc-to-markdown
or add devDependencies
entries to your package.json and run npm install:
package.json
{
"devDependencies": {
"@babel/cli": "^7.0.0-beta.40",
"@babel/core": "^7.0.0-beta.40",
"@babel/plugin-proposal-class-properties": "^7.0.0-beta.40",
"@babel/plugin-proposal-object-rest-spread": "^7.0.0-beta.40",
"@babel/preset-env": "^7.0.0-beta.40",
"@babel/preset-typescript": "^7.0.0-beta.40",
"jsdoc-babel": "^0.4.0-alpha.0",
"jsdoc-to-markdown": "^4.x"
}
}
Create jsdoc2md.json
file in project root, and add the following. You can the file as you wish. In case you choose a different name, change it in package.json
scripts too.
jsdoc2md.json
{
"source": {
"includePattern": ".+\\.(j|t)s(doc|x)?$",
"excludePattern": ".+\\.(test|spec).ts"
},
"plugins": [
"plugins/markdown",
"node_modules/jsdoc-babel"
],
"babel": {
"extensions": ["ts", "tsx"],
"ignore": ["**/*.(test|spec).ts"],
"babelrc": false,
"presets": [["@babel/preset-env", { "targets": { "node": "current" } }], "@babel/typescript"],
"plugins": ["@babel/proposal-class-properties", "@babel/proposal-object-rest-spread"]
}
}
This configuration:
- Excludes
your-file.test.ts
andyour-file.spec.ts
files from compilation and documentation. - Using @babel/preset-env, targets current node version for conversion. (You can change and test it according to your needs)
Add the following to the "scripts" section of your package.json
package.json
{
"scripts": {
"build:doc": "jsdoc2md --files 'src/**/*.ts' --configure jsdoc2md.json > README.md",
}
}
Babel and TypeScript removes some JSDoc comments during transpilation:
- babel/babel#6898: transform-flow-strip-types removes all jsdoc comments
- babel/babel#5512: Babel very strange move comments
Not so elegant, but I add a stub code below removed comments. For example
let STUB = 1;
/**
* Some description
* @typedef {Object} Config
* @property {string} name - Name of the config.
* @property {string} color - Color of choice.
*/
STUB = 1;
export type Config = {
name: string;
color: string;
};
As a preference, I use a template and add table of contents to my README.md
. Below are necessary configuration and files:
Install doctoc
npm install -save-dev doctoc
package.json
{
"scripts": {
"build:doc": "jsdoc2md --files 'src/**/*.ts' --configure jsdoc2md.json --template README.hbs > README.md && doctoc README.md"
}
}
README.hbs
<!-- DO NOT EDIT README.md (It will be overridden by README.hbs) -->
# name
One line description.
<!-- START doctoc -->
<!-- END doctoc -->
# Description
More detailed description
# Synopsis
Code samples
# API
{{>main~}}
- Home
- How jsdoc2md works
- Additional jsdoc tags supported
- Cherry picking which documentation appears in output
- Showcase ...
- Create ...
- How To ...
- How to use with npm run
- How to use with gulp
- How to create one output file per class
- How to document a AMD module
- How to document a CommonJS module (exports)
- How to document a CommonJS module (module.exports)
- How to document an ES2015 module (multiple named exports)
- How to document an ES2015 module (single default export)
- How to document Promises (using custom tags)
- How to document a ToDo list
- How to document ES2017 features
- How to document TypeScript
- The @typicalname tag
- Linking to external resources
- Param list format options
- Listing namepaths
- Troubleshooting