vorpal
vorpal copied to clipboard
Node's framework for interactive CLIs
Regression of https://github.com/dthree/vorpal/issues/60 Broken on `1.10.0`, `1.11.0` and `1.12.0` Confirmed working on `1.9.0`
Workaround incorrectly interpreted number-like values returned from minimist
This is an investigatory PR to study the introduction of a POSIX compliant shell code parser using bash-parser. There is a tween [PR on `cash` repo](https://github.com/dthree/cash/pull/112)
Tests and linter pass. Runs in Node without babel.
When returning an array of matches to autocomplete which begins with / it ignored the result. If trying to autocomplete "/t" with result [ "/test/" ] the match was discarded....
This PR aims to exit (detach the UI) after parser execution is complete.
Using `leven` package to calculate the difference between two strings. And displays similiar commands which have leven point smaller than 4. @dthree please check if I'm doing wrong.
Hi, I am trying below sample code on my MAC ` #!/usr/bin/env node const vorpal = require('vorpal')(); vorpal .command('say [words...]') .option('-b, --backwards') .option('-t, --twice') .action(function (args, callback) { let str...
When using arguments such as a hex string that could be interpreted as a numeric value: `mycommand 23782e8821` In lib/util.js, when that argument gets passed to minimist in the parseArgs...
Is there a way to call execSync without having the command entered into the command history? I have a few situations where I chain commands and it causes the history...