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

@mathieu_andrade/apidoc-markdown

v1.0.5

Published

Generate API documentation in markdown from apiDoc data.

Downloads

224

Readme

ApiDoc-markdown

npm badge

ApiDoc markdown creates a documentation from API descriptions in your source code.

It uses apidoc to convert inline documentation comments into json schema and later convert it to markdown.

Uses the apidoc-core library.

Documentation: apidocjs.com

Installation

$ npm install -g @mathieu_andrade/apidoc-markdown

Usage

Add some apidoc comments anywhere in your source code:

/**
 * @api {get} /user/:id Request User information
 * @apiName GetUser
 * @apiGroup User
 *
 * @apiParam {Number} id User's unique ID.
 *
 * @apiSuccess {String} firstname Firstname of the User.
 * @apiSuccess {String} lastname  Lastname of the User.
 */

Now generate the documentation from src/ into doc/.

$ apidoc-markdown -i src/ -o doc/

Most important cli commands

-f --file-filters <file-filters>         RegEx-Filter to select files that should be parsed (multiple -f can be used). (default: [])
-e, --exclude-filters <exclude-filters>  RegEx-Filter to select files / dirs that should not be parsed (many -e can be used). (default: [])
-i, --input <input>                      Input/source dirname. (default: [])
-o, --output <output>                    Output dirname. (default: "./doc/")
-t, --template <template>                Template to use for output files. Can be a path or a template type available. (default: "default.md")
-d, --data                               Return data files. (default: false)
-c, --config <config>                    Path to directory containing config file (apidoc.json). (default: "./")
-v, --verbose                            Verbose debug output.
--debug                                  Show debug messages.

Available templates can be found in templates directory.

Support

Please create a new issue if you have a suggestion/question or if you found a problem/bug.

Contributing

ApiDoc-markdown is a collaborative project. Pull requests are welcome. Please see the CONTRIBUTING file.

Todo

  • [ ] Improve gitbook template
  • [ ] Write Automated tests
  • [ ] Create a index file with all links of routes
  • [ ] Write a example
  • [ ] One file per route feature

Don't hesitate to suggest any feature you would like by creating an issue or a pull request.

License

The MIT license

Thanks

  • At apiDoc for the awesome apiDoc-core module
  • At rigwild for its huge work on the apiDoc-markdown module