Mic*_*ael 3 exec child-process node.js
我尝试使用 node.js(docker exec 命令)按顺序执行长进程。
我愿意:
const childProcess = require('child_process');
const execWithPromise = async command => {
return new Promise(async resolve => {
const process = childProcess.exec(command);
process.on('exit', err => resolve(err));
process.on('close', err => resolve(err));
});
};
const run = async () => {
await execWithPromise('/usr/local/bin/docker exec -i -t cucumber node long-running-script.js');
await execWithPromise('/usr/local/bin/docker exec -i -t cucumber node long-running-script.js');
};
run();
Run Code Online (Sandbox Code Playgroud)
但是承诺立即得到解决,结果为 1。在这两种情况下。该命令在命令行上运行得很好。
为什么会立即返回?
Pet*_*ger 10
child_process.exec期望回调作为第二个或第三个参数。它不返回承诺。根据您的用例和节点版本,您有几个选择。
使用回调并返回解析。
return new Promise(async resolve => {
childProcess.exec(command, (err, stout, sterr) {
resolve(err ? stout : sterr)
}
});
Run Code Online (Sandbox Code Playgroud)
改用 spawn(保留大部分代码)
const execWithPromise = async command => {
return new Promise(async (resolve, reject) => {
const process = childProcess.spawn(command);
process.on('data', data => resolve(data));
process.on('error', err => reject(err));
process.on('close', err => reject(err));
});
};
Run Code Online (Sandbox Code Playgroud)
使用 execSync 和 try catch
return new Promise(async (resolve, reject) => {
try {
resolve(childProcess.execSync(command));
} catch(error) {
reject(error)
}
});
Run Code Online (Sandbox Code Playgroud)
| 归档时间: |
|
| 查看次数: |
5881 次 |
| 最近记录: |