Lloyd Brookes

Hi @Myaamori, positional args are planned for the next release. In the meantime, you can emulate positional args with code like this. ```js const commandLineArgs = require('command-line-args') const optionDefinitions =...

Using the above example, if using command-line-usage the `positionals` option would appear in your usage guide (as @ghost mentioned above). See [here](https://github.com/75lb/command-line-usage/wiki/How-to-hide-an-option-in-the-usage-guide) for instructions how to hide it.

Hi, sorry for the delay. The `multiple` and `lazyMultiple` options are mutally exclusive - you should only set one of those options, not both. Yes, setting both options should throw...

yes, it's probably to do with that line. It's because `process.argv` almost always contains `node` and the script name as the first two items, e.g. `[ 'node', 'example.js', '--help' ]`....

You can see an example of how I format the output for markdown here (click "edit" to see the raw markdown): https://github.com/lwsjs/local-web-server/wiki/CLI-usage Does that help?

Have you made an progress with this issue? I don't have any immediate plans to build a markdown generator for CLI documentation, but maybe in the future..

Any update on a fix for this? This issue is preventing me switching to fast-glob from node-glob (without a breaking change).. ``` $ tree . ├── 1 │ ├── one...

[jsdoc-api](https://github.com/jsdoc2md/jsdoc-api) gives direct, programmatic access to the raw jsdoc output. It has sync, async and streaming interfaces. You can input source code as a string, a set of file names...

me too, but that option doesn't yet exist so...

yeah.. i added a synchronous method to do that.. can add Promise and streaming interfaces too if the demand is there.. see [jsdoc.renderSync([options])](https://github.com/jsdoc2md/jsdoc-api#module_jsdoc-api.renderSync).