使用Node.js child_process捕获致命错误

超、凢脫俗 2023-02-22 03:32 17阅读 0赞

I'm relatively new to hardcore Node.js hacking so I'm seeing all sorts of lovely new errors that I have no clue how to solve when I initially see them.  To this point I've managed to keep a smile on my face while trying to fix these errors, a quality I quite enjoy about myself.  One of the recent errors I encountered was with `child_process`, whereby an error would occur within an `execSync` command and the entire app would brick; not even  a `try/catch` would save me.  I did find a solution, however.

我对Node.js硬核入侵比较陌生，因此我看到各种各样可爱的新错误，当我初次看到这些错误时，我不知道如何解决。 到目前为止，在设法解决这些错误时，我一直保持笑容，这是我非常享受的一种品质。 我遇到的最近错误之一是`child_process` ，它在`execSync`命令中发生错误，整个应用程序变砖； 即使`try/catch`也无法拯救我。 我确实找到了解决方案。

## JavaScript **(**The JavaScript**)** ##

The best way to catch errors without letting your app brick is by using the process' `spawn` (or in this case `spawnSync`) method:

捕获错误而不让您的应用程序积木的最佳方法是使用进程的`spawn` (或在本例中为`spawnSync` )方法：

With this method you can check the `stderr` buffer first; if there's a String from it you know it errored out, if no error text then the process was clean!

使用这种方法，您可以首先检查`stderr`缓冲区； 如果有一个字符串，您就知道它出错了，如果没有错误文本，则说明过程很干净！

> 翻译自: [https://davidwalsh.name/catching-fatal-errors-nodejs-childprocess][https_davidwalsh.name_catching-fatal-errors-nodejs-childprocess]

[https_davidwalsh.name_catching-fatal-errors-nodejs-childprocess]: https://davidwalsh.name/catching-fatal-errors-nodejs-childprocess