- **no gotchas for users**: Seems obvious, but try typing "`npm install --save-dex`" instead of "`npm install --save-dev`" sometime. The command seems to execute successfully, but it doesn't save anything, because the misspelled flag was silently ignored. This lack of rigor plagues many familiar NodeJS tools, and can sometimes be very confusing and frustrating! For a great user experience, a command line parser should always strictly validate all arguments.

- **no gotchas for developers**: Many command-line libraries store their parsed data in a simple JavaScript hash object. This is convenient for small projects, but suppose a large project has many different source files that define and read parameters. If you try to read `data['output-dir']` when it wasn't defined, or if you misspell the key name, your tool will silently behave as if the parameter was omitted. And is `data['max-count']` a string or a number? Hard to tell! The **ts-command-line** library models each parameter type as a real TypeScript class.

- **automatic documentation**: Some command-line libraries treat the `--help` docs as a separate exercise for the reader. **ts-command-line** requires each every parameter to have a documentation string, and will automatically generates the `--help` for you. If you want to write long paragraphs, no problem -- they will be word-wrapped correctly. *[golf clap]*

- **structure and extensibility**: Instead of a simple function chain, **ts-command-line** provides a "scaffold" pattern that makes it easy to find and understand the command-line implementation for any tool project. The scaffold model is generally recommended, but there's also a "dynamic" model if you need it. (See below.)

Internally, **ts-command-line** is based on [argparse](https://www.npmjs.com/package/argparse) and the Python approach to command-lines. It doesn't provide zillions of alternative syntaxes and bells and whistles. But if you're looking for a simple, robust solution for your command-line, give it a try!