Use your AsyncAPI definition to generate literally anything. Markdown documentation, Node.js code, HTML documentation, anything!
⚠️ This package doesn't support AsyncAPI 1.x anymore. We recommend to upgrade to the latest AsyncAPI version using the AsyncAPI converter. If you need to convert documents on the fly, you may use the Node.js or Go converters.
npm install -g asyncapi-generatorOr use all the commands below using Docker by replacing ag in all the commands below with:
docker run --rm -it -v $PWD:/app -w /app asyncapi/generator [COMMAND HERE]  Usage: ag [options] <asyncapi> <template>
  Options:
    -V, --version                  output the version number
    -w, --watch                    watches the template directory and the AsyncAPI document for change, and re-generate the files when they occur.
    -o, --output <outputDir>       directory where to put the generated files (default: the current directory)
    -d, --disable-hook <hookName>  disable a specific hook
    -n, --no-overwrite <glob>      glob or path of the file(s) to skip when regenerating
    -p, --param <name=value>       additional param to pass to templates
    -t, --templates <templateDir>  directory where templates are located (default: Internal template folder)
    -h, --help                     output usage informationThe shortest possible syntax:
ag asyncapi.yaml markdownSpecify where to put the result:
ag -o ./docs asyncapi.yaml markdownPassing parameters to templates:
ag -o ./docs --param title='Hello from param' asyncapi.yaml markdownIn the template you can use it like this:  {{ params.title }}
To separate functionality into files, one can specify a filename like $$channel$$.js to generate a file for each channel defined in your AsyncAPI document. The following separations are supported: $$channel$$, $$message$$, $$schema$$, $$parameter$$ and $$securityScheme$$.
See API documentation.
See Authoring templates.
- Node.js v8.5+
 
Contributions are more than welcome. If you want to make a contribution, please make sure you go through the following steps:
- Pick or create an issue. It's always a good idea to leave a message saying that you're going to work on it before you start any actual work.
 - Fork the repository and work there.
 - Open a Pull Request pointing to 
masterbranch. - A maintainer will review and, eventually, merge your Pull Request. Please, be patient as most of us are doing this in our spare time.
 
Fran Méndez (@fmvilas)