In the command, when I run it in Grunt, I see the command output, but I don't see the command input:
So I want to see the command as it will be run in the terminal, as if I typed it myself.
I want to make sure that the command and its templates are being substituted correctly. Somehow I figured stdin: true might do it, but actually that defaults to true.
When the grunt step runs for that command all I see is the result. What I want to see is the { command: 'your-command-here' } being printed out in its entirety, post-template-substitution.
In the command, when I run it in Grunt, I see the command output, but I don't see the command input: So I want to see the command as it will be run in the terminal, as if I typed it myself.
I want to make sure that the command and its templates are being substituted correctly. Somehow I figured
stdin: true
might do it, but actually that defaults to true. When the grunt step runs for that command all I see is the result. What I want to see is the{ command: 'your-command-here' }
being printed out in its entirety, post-template-substitution.I have command strings like this:
and I would like to see, for instance
printed out on the console when running
grunt deploy-user-lambda-dev