A node.js (maybe common.js?) version of the Trollop ruby command line option parser
azpcu7
A simple but powerful command line parser for Node.js
Trollop is a commandline option parser for Ruby that just gets out of your way. **DEPRECATION** This gem has been renamed to optimist and will no longer be supported. Please switch to optimist as soon as possible.
Though Trollop has the ability to support subcommands, I find myself implementing the same logic repeatedly. The abstraction of this logic is now in trollop-subcommands. This provides a framework for parsing command line options for ruby scripts that have subcommands. The format is 'script_name [global_options] subcommand [subcommand_options]'. The framework supports all the typical scenarios around these type of command line scripts. All that need to be specified are the trollop configurations for the global options and each subcommand options. See the readme for more information.
This is a temporary gem with a patch, don't use it.
Bini needs no description.
Writing even complex command-line apps should be quick, easy and fun. Escort takes the excellent Trollop option parser and adds a whole bunch of awesome features to produce a library you will always want to turn to when a 'quick script' is in order.
Writing even complex command-line apps should be quick, easy and fun. Convoy takes the excellent Trollop option parser and adds a whole bunch of awesome features to produce a library you will always want to turn to when a 'quick script' is in order.
You've seen Getopt::Long, OptionParser, Thor? What the world needs now is one more command-line parser. This serves as a backend command line parser that passes the option-parsing portion of it off to OptionParser, Trollop, or any other option-parser that has an adapter[^adapter]. But the parts it *does* do are really exciting: It features arbitrarily deeply nested subcommands, optionally colorized help screens with smart formatting, automatically generated usage syntaxes, manpage generation[^maybe2], lazy-loading of subcommands, and (get this:) you can turn your command line app into a web app. (is processing a form then displaying a record really that different from CLI that does the same?)[^maybe3]