but the command line available ?
is impossible "detach" the command... anyone can help me?
also, how can i capture the output to a string rather than the console?
(context: i am trying to use this to build a command line for a telegram bot.)
Hello all, just a question. is it possible to run vorpal command that execute a background process/service, exiting from application/vorpal, connecting later again in a second and attach to the previous "process"?
I.e.: Running some vorpal commands (than running one or more background processes), exit from shell/ssh, connecting again running again the application and "reconnecting" so I can "resume" the UI and interact with the previous started processes? I hope I was clear. Thanks!
I.e.: Running some vorpal commands (than running one or more background processes), exit from shell/ssh, connecting again running again the application and "reconnecting" so I can "resume" the UI and interact with the previous started processes? I hope I was clear. Thanks!
Yes, something like this. For example, I run via vorpal command a bot (ie: a trading bot), a service in background, later on I can run again the vorpal application and interact with that service running other vorpal commands (see stats, check progress, stop bot, change configuration, restart it)
how can i embed vorpal in website?
Just started using Vorpal and got the basics in place...
node myapp.js will open an interactive session and prompt for commands; node myapp.js mycmd myarg will run a command and return to the command-prompt. Is there a way of giving one or more commands on the command-line and then switching to accepting commands interactively? At the moment, after command-definition, I've got vorpal.parse( process.argv ).show() ;. TIA
the second help isn't me typing it in
eugh
const commands = require('require-all')(__dirname + '/commands');
const _ = require("lodash")
_.forOwn(commands, function(value, key) {
vorpal.use(value)
});
Does Vorpal not have a way to do that automatically based on the command specified via the CLI? (I'm new here). Importing all the commands all at once is less performant than just importing the specific command that the user wants to execute. It will evaluate all the modules instead of just one. With various alternatives to Vorpal (commander.js, Caporal, sywac, etc) I've noticed much speed up in just importing specific modules only.
@yakuzadave ^
each command just follows this format:
module.exports = function(vorpal, options){
// insert vorpal command here
}
was following this bit of the docs as a guide:
https://github.com/dthree/vorpal/wiki/Docs-%7C-Creating-Extensions
https://github.com/dthree/vorpal/wiki/Docs-%7C-Creating-Extensions
Ideally, if the CLI has three commands a, b, and c, then running
the-cli a only imports and executes code from a.js while never touching files for b and c (or similar).
Now imagine the CLI has hundreds of commands, or commands with many options that import logic from different files.
But I suppose you can mitigate it by doing this (based on your snippet of code)
module.exports = function(vorpal, options){
const dep = require('dependency-needed-by-your-command')
dep.foo()
}instead of
const dep = require('dependency-needed-by-your-command')
module.exports = function(vorpal, options){
dep.foo()
}Each command imports all of its dependencies only when called.
But if you move the
require or import statements outside of the command functions, then it means when the index files loads all commands it will import every dependency for every command even if the commands aren't all used.
