Collectives™ on Stack Overflow

Find centralized, trusted content and collaborate around the technologies you use most.

Teams

Q&A for work

Connect and share knowledge within a single location that is structured and easy to search.

I'd like to use the execSync method which was added in NodeJS 0.12 but still have the output in the console window from which i ran the Node script.

E.g. if I run a NodeJS script which has the following line I'd like to see the full output of the rsync command "live" inside the console:

require('child_process').execSync('rsync -avAXz --info=progress2 "/src" "/dest"');
I understand that execSync returns the ouput of the command and that I could print that to the console after execution but this way I don't have "live" output...
You can pass the parent´s stdio to the child process if that´s what you want:
require('child_process').execSync(
    'rsync -avAXz --info=progress2 "/src" "/dest"',
    {stdio: 'inherit'}
                It means that the child process will use the parent's stdin, stdout and stderr streams. So when the child process writes to either of them, it will actually be written directly to the parent´s stream.
– gregers
                Oct 7, 2015 at 21:00
                This is a very valuable answer, as the official documentation is not really explicit about the expected syntax.
– chikamichi
                Dec 18, 2015 at 0:13
                Instead of [0,1,2] I've used 'inherit', which is equivalent to [process.stdin, process.stdout, process.stderr] or [0,1,2] as per docs
– Kurt
                May 2, 2016 at 0:30
                @Booligoosh Instead of simply adding {stdio:'inherit'}, you have to add .toString() and then call console.log manually with the result. In addition, it doesn't even fulfill the questions requirement of seeing the command output "live". I don't think it's "much simpler", in fact I don't think it's simpler at all.
– boileau
                Nov 13, 2017 at 9:28
You can simply use .toString().
var result = require('child_process').execSync('rsync -avAXz --info=progress2 "/src" "/dest"').toString();
console.log(result);
Edit: Looking back on this, I've realised that it doesn't actually answer the specific question because it doesn't show the output to you 'live' — only once the command has finished running.
However, I'm leaving this answer here because I know quite a few people come across this question just looking for how to print the result of the command after execution.
                This doesn't work on failure (status code != 0) because .execSync() throws an Error instance.
– Álvaro González
                Jun 28, 2017 at 7:13
                Doesn't work for me, i.e. output is only written after command finishes. Does this apply to a specific version? my node -v: v6.3.1
– etov
                Sep 28, 2017 at 8:43
                Please consider updating the answer to note it's applicable only to certain node versions - this would make it more useful to others
– etov
                Sep 28, 2017 at 12:00
                Downvote since ti's in now way relating to the question regarding output during the command is executed.
– karfau
                Jan 11, 2020 at 22:16
Unless you redirect stdout and stderr as the accepted answer suggests, this is not possible with execSync or spawnSync.  Without redirecting stdout and stderr those commands only return stdout and stderr when the command is completed.
To do this without redirecting stdout and stderr, you are going to need to use spawn to do this but it's pretty straight forward:
var spawn = require('child_process').spawn;
//kick off process of listing files
var child = spawn('ls', ['-l', '/']);
//spit stdout to screen
child.stdout.on('data', function (data) {   process.stdout.write(data.toString());  });
//spit stderr to screen
child.stderr.on('data', function (data) {   process.stdout.write(data.toString());  });
child.on('close', function (code) { 
    console.log("Finished with code " + code);
I used an ls command that recursively lists files so that you can test it quickly.  Spawn takes as first argument the executable name you are trying to run and as it's second argument it takes an array of strings representing each parameter you want to pass to that executable.
However, if you are set on using execSync and can't redirect stdout or stderr for some reason, you can open up another terminal like xterm and pass it a command like so:
var execSync = require('child_process').execSync;
execSync("xterm -title RecursiveFileListing -e ls -latkR /");
This will allow you to see what your command is doing in the new terminal but still have the synchronous call.
                The example using spawn may be correct, but the opening statement about not being about to use execSync is not accurate. See answer from @gregers
– AgDude
                Dec 24, 2015 at 15:46
    const cmd = 'git rev-parse --is-inside-work-tree';
    execSync(cmd).toString();
 } catch (error) {
    console.log(`Status Code: ${error.status} with '${error.message}'`;
Ref: https://stackoverflow.com/a/43077917/104085
// nodejs
var execSync = require('child_process').execSync;
// typescript
const { execSync } = require("child_process");
 try {
    const cmd = 'git rev-parse --is-inside-work-tree';
    execSync(cmd).toString();
 } catch (error) {
    error.status;  // 0 : successful exit, but here in exception it has to be greater than 0
    error.message; // Holds the message you typically want.
    error.stderr;  // Holds the stderr output. Use `.toString()`.
    error.stdout;  // Holds the stdout output. Use `.toString()`.
When command runs successful:
                The pictures have console.log( but the code text just calls .toString(); and throws away the string result. This would only work if run in the interactive console, not in a script.
– Carl Walsh
                May 5 at 6:04
        
Thanks for contributing an answer to Stack Overflow!
Please be sure to answer the question. Provide details and share your research!
But avoid …
Asking for help, clarification, or responding to other answers.
Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.