blocks|key|3004758|text|这在Node.js中是不可能的，因为child_process.spawn和child_process.exec都是从头开始构建成异步的。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|3004759|有关详情，请参阅：https://github.com/ry/node/blob/master/lib/child_process.js|3004760|如果你真的想要这个阻塞，然后把之后需要发生的一切都放在一个回调中，或者建立你自己的队列来以阻塞的方式处理这个问题，我想你可以使用Async.js来完成这个任务。|3004761|或者，如果你有太多的时间可以花，你可以自己在Node.js上修改一下。|3004762|entityMap|0|LINK|mutability|MUTABLE|url|https://github.com/ry/node/blob/master/lib/child_process.js|1|https://github.com/caolan/async/^0|I|J|12|I|0|9|1N|0|0|1S|8|1|0|0^^$0|@$1|2|3|4|5|6|7|V|8|@$9|W|A|X|B|C]|$9|Y|A|Z|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|10|8|@]|D|@$9|11|A|12|1|13]]|E|$]]|$1|H|3|I|5|6|7|14|8|@]|D|@$9|15|A|16|1|17]]|E|$]]|$1|J|3|K|5|6|7|18|8|@]|D|@]|E|$]]|$1|L|3|-4|5|6|7|19|8|@]|D|@]|E|$]]]|M|$N|$5|O|P|Q|E|$R|S]]|T|$5|O|P|Q|E|$R|U]]]]

This is not possible in Node.js, both <code>child_process.spawn</code> and <code>child_process.exec</code> were built from the ground up to be async.

For details see: <a href="https://github.com/ry/node/blob/master/lib/child_process.js" rel="noreferrer">https://github.com/ry/node/blob/master/lib/child_process.js</a>

If you really want to have this blocking, then put everything that needs to happen afterwards in a callback, or build your own queue to handle this in a blocking fashion, I suppose you could use <a href="https://github.com/caolan/async/" rel="noreferrer">Async.js</a> for this task.

Or, in case you have way too much time to spend, hack around in Node.js it self.

blocks|key|3218365|text|请参见execSync库。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|3218366|使用node-ffi很容易做到这一点。我不建议用于服务器进程，但对于一般的开发实用程序，它可以完成任务。安装库。|3218367|npm+install+node-ffi|code-block|syntax|javascript|3218368|示例脚本：|3218369|var+FFI+=+require("node-ffi");
var+libc+=+new+FFI.Library(null,+{
++"system":+["int32",+["string"]]
});

var+run+=+libc.system;
run("echo+$USER");|3218370|编辑2012年6月:如何获取STDOUT|3218371|var+lib+=+ffi.Library(null,+{
++++//+FILE*+popen(char*+cmd,+char*+mode);
++++popen:+['pointer',+['string',+'string']],

++++//+void+pclose(FILE*+fp);
++++pclose:+['void',+[+'pointer']],

++++//+char*+fgets(char*+buff,+int+buff,+in)
++++fgets:+['string',+['string',+'int','pointer']]
});

function+execSync(cmd)+{
++var
++++buffer+=+new+Buffer(1024),
++++result+=+"",
++++fp+=+lib.popen(cmd,+'r');

++if+(!fp)+throw+new+Error('execSync+error:+'%2Bcmd);

++while(lib.fgets(buffer,+1024,+fp))+{
++++result+%2B=+buffer.readCString();
++};
++lib.pclose(fp);

++return+result;
}

console.log(execSync('echo+$HOME'));|3218372|entityMap|0|LINK|mutability|MUTABLE|url|https://github.com/mgutz/execSync|1|https://github.com/rbranson/node-ffi^0|3|8|0|0|2|8|1|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|12|8|@]|9|@$A|13|B|14|1|15]]|C|$]]|$1|D|3|E|5|6|7|16|8|@]|9|@$A|17|B|18|1|19]]|C|$]]|$1|F|3|G|5|H|7|1A|8|@]|9|@]|C|$I|J]]|$1|K|3|L|5|6|7|1B|8|@]|9|@]|C|$]]|$1|M|3|N|5|H|7|1C|8|@]|9|@]|C|$I|J]]|$1|O|3|P|5|6|7|1D|8|@]|9|@]|C|$]]|$1|Q|3|R|5|H|7|1E|8|@]|9|@]|C|$I|J]]|$1|S|3|-4|5|6|7|1F|8|@]|9|@]|C|$]]]|T|$U|$5|V|W|X|C|$Y|Z]]|10|$5|V|W|X|C|$Y|11]]]]

See <a href="https://github.com/mgutz/execSync">execSync</a> library.

It's fairly easy to do with <a href="https://github.com/rbranson/node-ffi">node-ffi</a>. I wouldn't recommend for server processes, but for general development utilities it gets things done. Install the library.

<pre><code>npm install node-ffi
</code></pre>

Example script:

<pre><code>var FFI = require("node-ffi");
var libc = new FFI.Library(null, {
 "system": ["int32", ["string"]]
});

var run = libc.system;
run("echo $USER");
</code></pre>

[EDIT Jun 2012: How to get STDOUT]

<pre><code>var lib = ffi.Library(null, {
 // FILE* popen(char* cmd, char* mode);
 popen: ['pointer', ['string', 'string']],

 // void pclose(FILE* fp);
 pclose: ['void', [ 'pointer']],

 // char* fgets(char* buff, int buff, in)
 fgets: ['string', ['string', 'int','pointer']]
});

function execSync(cmd) {
 var
 buffer = new Buffer(1024),
 result = "",
 fp = lib.popen(cmd, 'r');

 if (!fp) throw new Error('execSync error: '+cmd);

 while(lib.fgets(buffer, 1024, fp)) {
 result += buffer.readCString();
 };
 lib.pclose(fp);

 return result;
}

console.log(execSync('echo $HOME'));
</code></pre>

blocks|key|3004783|text|我习惯于在回调函数的末尾实现"synchronous"内容。不是很好，但很管用。如果需要实现一系列命令行执行，则需要将exec包装到某个命名函数中并递归调用它。这个模式似乎对我很有用：|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|3004784|SeqOfExec(someParam);

function+SeqOfExec(somepParam)+{
++++//+some+stuff
++++//+.....
++++//+.....

++++var+execStr+=+"yourExecString";
++++child_proc.exec(execStr,+function+(error,+stdout,+stderr)+{
++++++++if+(error+!=+null)+{
++++++++++++if+(stdout)+{
++++++++++++++++throw+Error("Smth+goes+wrong"+%2B+error);
++++++++++++}+else+{
++++++++++++++++//+consider+that+empty+stdout+causes
++++++++++++++++//+creation+of+error+object
++++++++++++}
++++++++}
++++++++//+some+stuff
++++++++//+.....
++++++++//+.....

++++++++//+you+also+need+some+flag+which+will+signal+that+you+
++++++++//+need+to+end+loop
++++++++if+(someFlag+)+{
++++++++++++//+your+synch+stuff+after+all+execs
++++++++++++//+here
++++++++++++//+.....
++++++++}+else+{
++++++++++++SeqOfExec(someAnotherParam);
++++++++}
++++});
};|code-block|syntax|javascript|3004785|entityMap^0|E|D|1N|4|0|0^^$0|@$1|2|3|4|5|6|7|M|8|@$9|N|A|O|B|C]|$9|P|A|Q|B|C]]|D|@]|E|$]]|$1|F|3|G|5|H|7|R|8|@]|D|@]|E|$I|J]]|$1|K|3|-4|5|6|7|S|8|@]|D|@]|E|$]]]|L|$]]

I get used to implement <code>"synchronous"</code> stuff at the end of the callback function. Not very nice, but it works. If you need to implement a sequence of command line executions you need to wrap <code>exec</code> into some named function and recursively call it.
This pattern seem to be usable for me:

<pre><code>SeqOfExec(someParam);

function SeqOfExec(somepParam) {
 // some stuff
 // .....
 // .....

 var execStr = "yourExecString";
 child_proc.exec(execStr, function (error, stdout, stderr) {
 if (error != null) {
 if (stdout) {
 throw Error("Smth goes wrong" + error);
 } else {
 // consider that empty stdout causes
 // creation of error object
 }
 }
 // some stuff
 // .....
 // .....

 // you also need some flag which will signal that you 
 // need to end loop
 if (someFlag ) {
 // your synch stuff after all execs
 // here
 // .....
 } else {
 SeqOfExec(someAnotherParam);
 }
 });
};
</code></pre>

blocks|key|291195|text|您可以在nodejs中进行同步shell操作，如下所示：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|291196|var+execSync+=+function(cmd)+{

++++var+exec++=+require('child_process').exec;
++++var+fs+=+require('fs');

++++//for+linux+use+;+instead+of+&&
++++//execute+your+command+followed+by+a+simple+echo+
++++//to+file+to+indicate+process+is+finished
++++exec(cmd+%2B+"+>+c:\\stdout.txt+&&+echo+done+>+c:\\sync.txt");

++++while+(true)+{
++++++++//consider+a+timeout+option+to+prevent+infinite+loop
++++++++//NOTE:+this+will+max+out+your+cpu+too!
++++++++try+{
++++++++++++var+status+=+fs.readFileSync('c:\\sync.txt',+'utf8');

++++++++++++if+(status.trim()+==+"done")+{
++++++++++++++++var+res+=+fs.readFileSync("c:\\stdout.txt",+'utf8');
++++++++++++++++fs.unlinkSync("c:\\stdout.txt");+//cleanup+temp+files
++++++++++++++++fs.unlinkSync("c:\\sync.txt");
++++++++++++++++return+res;
++++++++++++}
++++++++}+catch(e)+{+}+//readFileSync+will+fail+until+file+exists
++++}

};

//won't+return+anything,+but+will+take+10+seconds+to+run
console.log(execSync("sleep+10"));+

//assuming+there+are+a+lot+of+files+and+subdirectories,+
//this+too+may+take+a+while,+use+your+own+applicable+file+path
console.log(execSync("dir+/s+c:\\usr\\docs\\"));|code-block|syntax|javascript|291197|编辑-此示例适用于windows环境，如有必要，请根据您自己的linux需求进行调整。|291198|entityMap^0|0|0|0^^$0|@$1|2|3|4|5|6|7|K|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|L|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|M|8|@]|9|@]|A|$]]|$1|I|3|-4|5|6|7|N|8|@]|9|@]|A|$]]]|J|$]]

you can do synchronous shell operations in nodejs like so:

<pre><code>var execSync = function(cmd) {

 var exec = require('child_process').exec;
 var fs = require('fs');

 //for linux use ; instead of &amp;&amp;
 //execute your command followed by a simple echo 
 //to file to indicate process is finished
 exec(cmd + " &gt; c:\\stdout.txt &amp;&amp; echo done &gt; c:\\sync.txt");

 while (true) {
 //consider a timeout option to prevent infinite loop
 //NOTE: this will max out your cpu too!
 try {
 var status = fs.readFileSync('c:\\sync.txt', 'utf8');

 if (status.trim() == "done") {
 var res = fs.readFileSync("c:\\stdout.txt", 'utf8');
 fs.unlinkSync("c:\\stdout.txt"); //cleanup temp files
 fs.unlinkSync("c:\\sync.txt");
 return res;
 }
 } catch(e) { } //readFileSync will fail until file exists
 }

};

//won't return anything, but will take 10 seconds to run
console.log(execSync("sleep 10")); 

//assuming there are a lot of files and subdirectories, 
//this too may take a while, use your own applicable file path
console.log(execSync("dir /s c:\\usr\\docs\\"));
</code></pre>

EDIT - this example is meant for windows environments, adjust for your own linux needs if necessary

blocks|key|291200|text|在node.js中有一个很好的流量控制模块，叫做asyncblock。如果将代码包装在函数中对于您的情况是可以的，则可以考虑使用以下示例：|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|291201|var+asyncblock+=+require('asyncblock');
var+exec+=+require('child_process').exec;

asyncblock(function+(flow)+{
++++exec('node+-v',+flow.add());
++++result+=+flow.wait();
++++console.log(result);++++//+There'll+be+trailing+\n+in+the+output

++++//+Some+other+jobs
++++console.log('More+results+like+if+it+were+sync...');
});|code-block|syntax|javascript|291202|entityMap|0|LINK|mutability|MUTABLE|url|https://github.com/scriby/asyncblock^0|O|A|0|0|0^^$0|@$1|2|3|4|5|6|7|Q|8|@]|9|@$A|R|B|S|1|T]]|C|$]]|$1|D|3|E|5|F|7|U|8|@]|9|@]|C|$G|H]]|$1|I|3|-4|5|6|7|V|8|@]|9|@]|C|$]]]|J|$K|$5|L|M|N|C|$O|P]]]]

There's an excellent module for flow control in node.js called <a href="https://github.com/scriby/asyncblock" rel="noreferrer">asyncblock</a>. If wrapping the code in a function is OK for your case, the following sample may be considered:

<pre><code>var asyncblock = require('asyncblock');
var exec = require('child_process').exec;

asyncblock(function (flow) {
 exec('node -v', flow.add());
 result = flow.wait();
 console.log(result); // There'll be trailing \n in the output

 // Some other jobs
 console.log('More results like if it were sync...');
});
</code></pre>

blocks|key|287931|text|您可以使用纤程来实现这一点。例如，使用我的Common+Node+library，代码将如下所示：|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|287932|result+=+require('subprocess').command('node+-v');|code-block|syntax|javascript|287933|entityMap|0|LINK|mutability|MUTABLE|url|https://github.com/olegp/common-node^0|L|J|0|0|0^^$0|@$1|2|3|4|5|6|7|Q|8|@]|9|@$A|R|B|S|1|T]]|C|$]]|$1|D|3|E|5|F|7|U|8|@]|9|@]|C|$G|H]]|$1|I|3|-4|5|6|7|V|8|@]|9|@]|C|$]]]|J|$K|$5|L|M|N|C|$O|P]]]]

You can achieve this using fibers. For example, using my <a href="https://github.com/olegp/common-node" rel="noreferrer">Common Node library</a>, the code would look like this:

<pre><code>result = require('subprocess').command('node -v');
</code></pre>

blocks|key|287939|text|这是我发现的最简单的方法：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|287940|287941|+exec-同步：https://github.com/jeremyfa/node-exec-sync|blockquote|offset|length|style|BOLD|287942|287943|(不要与execSync混淆。)同步执行shell命令。将其用于迁移脚本、cli程序，但不用于常规服务器代码。|287944|示例：|287945|287946|var+execSync+=+require('exec-sync');+++
var+user+=+execSync('echo+$USER');
console.log(user);|code-block|syntax|javascript|287947|entityMap|0|LINK|mutability|MUTABLE|url|https://github.com/jeremyfa/node-exec-sync^0|0|0|1|7|9|16|0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|12|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|13|8|@]|9|@]|A|$]]|$1|C|3|D|5|E|7|14|8|@$F|15|G|16|H|I]]|9|@$F|17|G|18|1|19]]|A|$]]|$1|J|3|-4|5|6|7|1A|8|@]|9|@]|A|$]]|$1|K|3|L|5|6|7|1B|8|@]|9|@]|A|$]]|$1|M|3|N|5|6|7|1C|8|@]|9|@]|A|$]]|$1|O|3|-4|5|6|7|1D|8|@]|9|@]|A|$]]|$1|P|3|Q|5|R|7|1E|8|@]|9|@]|A|$S|T]]|$1|U|3|-4|5|6|7|1F|8|@]|9|@]|A|$]]]|V|$W|$5|X|Y|Z|A|$10|11]]]]

This is the easiest way I found:

<blockquote>
 exec-Sync: 
 <a href="https://github.com/jeremyfa/node-exec-sync" rel="noreferrer">https://github.com/jeremyfa/node-exec-sync</a>
 (Not to be confused with execSync.)
 
 Execute shell command synchronously. Use this for migration scripts, cli programs, but not for regular server code.
 
 Example:
</blockquote>

<pre><code>var execSync = require('exec-sync'); 
var user = execSync('echo $USER');
console.log(user);
</code></pre>

blocks|key|3005000|text|实际上，我遇到过这样一种情况:我需要从package.json预安装脚本中一个接一个地运行多个命令，而这种方式既可以在Windows上运行，也可以在Linux/OSX上运行，所以我不能依赖非核心模块。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3005001|所以这就是我想出来的：|3005002|#cmds.coffee
childproc+=+require+'child_process'

exports.exec+=+(cmds)+->
++next+=+->
++++if+cmds.length+>+0
++++++cmd+=+cmds.shift()
++++++console.log+"Running+command:+#{cmd}"
++++++childproc.exec+cmd,+(err,+stdout,+stderr)+->
++++++++if+err?+then+console.log+err
++++++++if+stdout?+then+console.log+stdout
++++++++if+stderr?+then+console.log+stderr
++++++++next()
++++else
++++++console.log+"Done+executing+commands."

++console.log+"Running+the+follows+commands:"
++console.log+cmds
++next()|code-block|syntax|javascript|3005003|你可以这样使用它：|3005004|require('./cmds').exec+['grunt+coffee',+'nodeunit+test/tls-config.js']|3005005|EDIT:如上所述，这实际上并不返回输出，也不允许您在Node程序中使用命令的结果。另一个想法是使用LiveScript回调。http://livescript.net/|offset|length|3005006|entityMap|0|LINK|mutability|MUTABLE|url|http://livescript.net/^0|0|0|0|0|0|1R|M|0|0^^$0|@$1|2|3|4|5|6|7|Y|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|Z|8|@]|9|@]|A|$]]|$1|D|3|E|5|F|7|10|8|@]|9|@]|A|$G|H]]|$1|I|3|J|5|6|7|11|8|@]|9|@]|A|$]]|$1|K|3|L|5|F|7|12|8|@]|9|@]|A|$G|H]]|$1|M|3|N|5|6|7|13|8|@]|9|@$O|14|P|15|1|16]]|A|$]]|$1|Q|3|-4|5|6|7|17|8|@]|9|@]|A|$]]]|R|$S|$5|T|U|V|A|$W|X]]]]

I actually had a situation where I needed to run multiple commands one after another from a package.json preinstall script in a way that would work on both Windows and Linux/OSX, so I couldn't rely on a non-core module.

So this is what I came up with:

<pre class="lang-cs prettyprint-override"><code>#cmds.coffee
childproc = require 'child_process'

exports.exec = (cmds) -&gt;
 next = -&gt;
 if cmds.length &gt; 0
 cmd = cmds.shift()
 console.log "Running command: #{cmd}"
 childproc.exec cmd, (err, stdout, stderr) -&gt;
 if err? then console.log err
 if stdout? then console.log stdout
 if stderr? then console.log stderr
 next()
 else
 console.log "Done executing commands."

 console.log "Running the follows commands:"
 console.log cmds
 next()
</code></pre>

You can use it like this:

<pre class="lang-cs prettyprint-override"><code>require('./cmds').exec ['grunt coffee', 'nodeunit test/tls-config.js']
</code></pre>

EDIT: as pointed out, this doesn't actually return the output or allow you to use the result of the commands in a Node program. One other idea for that is to use LiveScript backcalls. <a href="http://livescript.net/" rel="nofollow">http://livescript.net/</a>

blocks|key|285867|text|只是补充一下，尽管在应该使用它们的地方用例很少，但spawnSync+/+execFileSync+/+execSync是在以下提交中添加到node.js中的：https://github.com/joyent/node/compare/d58c206862dc...e8df2676748e|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|285868|entityMap|0|LINK|mutability|MUTABLE|url|https://github.com/joyent/node/compare/d58c206862dc...e8df2676748e^0|P|9|11|C|1G|8|28|1U|0|0^^$0|@$1|2|3|4|5|6|7|N|8|@$9|O|A|P|B|C]|$9|Q|A|R|B|C]|$9|S|A|T|B|C]]|D|@$9|U|A|V|1|W]]|E|$]]|$1|F|3|-4|5|6|7|X|8|@]|D|@]|E|$]]]|G|$H|$5|I|J|K|E|$L|M]]]]

Just to add that even though there are few usecases where you should use them, <code>spawnSync</code> / <code>execFileSync</code> / <code>execSync</code> were added to node.js in these commits: <a href="https://github.com/joyent/node/compare/d58c206862dc...e8df2676748e">https://github.com/joyent/node/compare/d58c206862dc...e8df2676748e</a>

blocks|key|3218748|text|使用ShellJS模块。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|3218749|不提供回调的exec函数。|3218750|示例：|3218751|var+version+=+exec('node+-v').output;|code-block|syntax|javascript|3218752|entityMap|0|LINK|mutability|MUTABLE|url|https://github.com/arturadib/shelljs|1|https://github.com/arturadib/shelljs#execcommand--options--callback^0|2|7|0|0|6|4|1|0|0|0^^$0|@$1|2|3|4|5|6|7|W|8|@]|9|@$A|X|B|Y|1|Z]]|C|$]]|$1|D|3|E|5|6|7|10|8|@]|9|@$A|11|B|12|1|13]]|C|$]]|$1|F|3|G|5|6|7|14|8|@]|9|@]|C|$]]|$1|H|3|I|5|J|7|15|8|@]|9|@]|C|$K|L]]|$1|M|3|-4|5|6|7|16|8|@]|9|@]|C|$]]]|N|$O|$5|P|Q|R|C|$S|T]]|U|$5|P|Q|R|C|$S|V]]]]

Use <a href="https://github.com/arturadib/shelljs" rel="noreferrer">ShellJS</a> module.

<a href="https://github.com/arturadib/shelljs#execcommand--options--callback" rel="noreferrer">exec</a> function without providing callback.

Example:

<pre><code>var version = exec('node -v').output;
</code></pre>

blocks|key|3005018|text|Node.js+(从0.12版开始--暂时)支持execSync|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|3005019|child_process.execSync(command[,+options])|code-block|syntax|javascript|3005020|您现在可以直接执行此操作：|3005021|const+execSync+=+require('child_process').execSync;
code+=+execSync('node+-v');|3005022|它会做你所期望的事情。(默认情况下，通过管道将i/o结果传送到父进程)。请注意，您现在也可以使用spawnSync。|3005023|entityMap|0|LINK|mutability|MUTABLE|url|https://nodejs.org/api/child_process.html#child_process_child_process_execsync_command_options|1|https://nodejs.org/api/child_process.html#child_process_child_process_spawnsync_command_args_options^0|O|8|O|8|0|0|0|0|0|1C|9|1C|9|1|0^^$0|@$1|2|3|4|5|6|7|10|8|@$9|11|A|12|B|C]]|D|@$9|13|A|14|1|15]]|E|$]]|$1|F|3|G|5|H|7|16|8|@]|D|@]|E|$I|J]]|$1|K|3|L|5|6|7|17|8|@]|D|@]|E|$]]|$1|M|3|N|5|H|7|18|8|@]|D|@]|E|$I|J]]|$1|O|3|P|5|6|7|19|8|@$9|1A|A|1B|B|C]]|D|@$9|1C|A|1D|1|1E]]|E|$]]|$1|Q|3|-4|5|6|7|1F|8|@]|D|@]|E|$]]]|R|$S|$5|T|U|V|E|$W|X]]|Y|$5|T|U|V|E|$W|Z]]]]

Node.js (since version 0.12 - so for a while) supports <a href="https://nodejs.org/api/child_process.html#child_process_child_process_execsync_command_options" rel="noreferrer"><code>execSync</code></a>:

<pre><code>child_process.execSync(command[, options])
</code></pre>

You can now directly do this:

<pre><code>const execSync = require('child_process').execSync;
code = execSync('node -v');
</code></pre>

and it'll do what you expect. (Defaults to pipe the i/o results to the parent process). Note that you can also <a href="https://nodejs.org/api/child_process.html#child_process_child_process_spawnsync_command_args_options" rel="noreferrer"><code>spawnSync</code></a> now.

blocks|key|288924|text|本机Node.js解决方案是：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|288925|const+{execSync}+=+require('child_process');

const+result+=+execSync('node+-v');+//++this+do+the+trick+|code-block|syntax|javascript|288926|288927|const+result+=+execSync('git+rev-parse+HEAD',+{encoding:+'utf8'});|288928|..。在sync+exec上设置超时也很好：|288929|const+result+=+execSync('git+rev-parse+HEAD',+{encoding:+'utf8',+timeout:+10000});|288930|entityMap^0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|P|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|Q|8|@]|9|@]|A|$E|F]]|$1|G|3|-4|5|6|7|R|8|@]|9|@]|A|$]]|$1|H|3|I|5|D|7|S|8|@]|9|@]|A|$E|F]]|$1|J|3|K|5|6|7|T|8|@]|9|@]|A|$]]|$1|L|3|M|5|D|7|U|8|@]|9|@]|A|$E|F]]|$1|N|3|-4|5|6|7|V|8|@]|9|@]|A|$]]]|O|$]]

Native Node.js solution is:
<pre><code>const {execSync} = require('child_process');

const result = execSync('node -v'); // this do the trick 
</code></pre>
Just be aware that some commands returns <code>Buffer</code> instead of <code>string</code>. And if you need <code>string</code> just add <code>encoding</code> to execSync options:
<pre><code>const result = execSync('git rev-parse HEAD', {encoding: 'utf8'});
</code></pre>
... and it is also good to have timeout on sync exec:
<pre><code>const result = execSync('git rev-parse HEAD', {encoding: 'utf8', timeout: 10000});
</code></pre>

blocks|key|3218939|text|我从5年来的方式是有2行；|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3218940|const+{+execSync+}+=+require('child_process');
const+shell+=+(cmd)+=>+execSync(cmd,+{encoding:+'utf8'});|code-block|syntax|javascript|3218941|然后享受：shell('git+remote+-v')或out+=+shell('ls+-l')+..等等|offset|length|style|CODE|3218942|entityMap^0|0|0|5|M|S|K|0^^$0|@$1|2|3|4|5|6|7|O|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|P|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|Q|8|@$I|R|J|S|K|L]|$I|T|J|U|K|L]]|9|@]|A|$]]|$1|M|3|-4|5|6|7|V|8|@]|9|@]|A|$]]]|N|$]]

my way since 5 years is to have 2 lines ;
<pre class="lang-sh prettyprint-override"><code>const { execSync } = require('child_process');
const shell = (cmd) =&gt; execSync(cmd, {encoding: 'utf8'});
</code></pre>
Then enjoy:
<code>shell('git remote -v')</code>
or
<code>out = shell('ls -l')</code>
.. so on

I need in node.js function

<pre><code>result = execSync('node -v');
</code></pre>

that will synchronously execute the given command line and return all stdout'ed by that command text.

<blockquote>
 ps. Sync is wrong. I know. Just for personal use.
</blockquote>

UPDATE

Now we have mgutz's solution which gives us exit code, but not stdout! Still waiting for a more precise answer.

UPDATE

mgutz updated his answer and the solution is here :) 
Also, as dgo.a mentioned, there is stand-alone module <a href="https://github.com/jeremyfa/node-exec-sync" rel="noreferrer">exec-sync</a>

UPDATE 2014-07-30

<a href="https://github.com/arturadib/shelljs" rel="noreferrer">ShellJS</a> lib arrived. Consider this is the best choice for now.

<hr>

UPDATE 2015-02-10

AT LAST! NodeJS 0.12 supports <code>execSync</code> natively. 
See official <a href="http://nodejs.org/docs/v0.12.0/api/child_process.html#child_process_child_process_execsync_command_options" rel="noreferrer">docs</a>

node.js execute system command synchronously

服务器

Windows

Linux

我需要在node.js中使用函数result = execSync('node -v');这将同步，并执行给定的命令行，并返回该命令文本所包含的所有标准输出。 ps。同步错误。我知道呀。仅供个人使用。更新现在我们有了mgutz的解决方案，它给了我们退出代码，而不是stdout！还在等待一个更准确的答案。更新mgutz更...

问node.js同步执行系统命令
EN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问node.js同步执行系统命令EN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问node.js同步执行系统命令
EN