-
Notifications
You must be signed in to change notification settings - Fork 151
Troubleshooting
Lloyd Brookes edited this page Nov 17, 2016
·
3 revisions
- Why am I getting errors?
As a general rule, if it works in jsdoc it will work in jsdoc2md. Test your source with jsdoc -X my-code.js
- if that fails it will fail in jsdoc2md too.
- Why isn't my namepath being converted to a link?
All tags requiring a namepath argument, for example @requires module:something
, should render as a link. For it to work, the namepath specified must be valid and point to an identifier in one of the files being parsed by jsdoc2md. To get a list of the valid namepaths in your sourcecode, run jsdoc2md --namepaths lib/*.js
.
- 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