如果你只想记录错误的堆栈跟踪(而不是错误消息)，Node 6及以上会自动在堆栈跟踪中包含错误名称和消息，如果你想做一些自定义错误处理，这有点烦人:

console.log (error.stack.replace(错误。信息,”)

这个解决方案将只记录错误名称和堆栈跟踪(因此，例如，您可以格式化错误消息，并在代码中的其他地方以您希望的方式显示它)。

上面的例子只打印错误名称，后面跟着堆栈跟踪，例如:

Error: 
    at /Users/cfisher/Git/squashed/execProcess.js:6:17
    at ChildProcess.exithandler (child_process.js:213:5)
    at emitTwo (events.js:106:13)
    at ChildProcess.emit (events.js:191:7)
    at maybeClose (internal/child_process.js:877:16)
    at Socket.<anonymous> (internal/child_process.js:334:11)
    at emitOne (events.js:96:13)
    at Socket.emit (events.js:188:7)
    at Pipe._handle.close [as _onclose] (net.js:498:12)

而不是:

Error: Error: Command failed: sh ./commands/getBranchCommitCount.sh HEAD
git: 'rev-lists' is not a git command. See 'git --help'.

Did you mean this?
        rev-list

    at /Users/cfisher/Git/squashed/execProcess.js:6:17
    at ChildProcess.exithandler (child_process.js:213:5)
    at emitTwo (events.js:106:13)
    at ChildProcess.emit (events.js:191:7)
    at maybeClose (internal/child_process.js:877:16)
    at Socket.<anonymous> (internal/child_process.js:334:11)
    at emitOne (events.js:96:13)
    at Socket.emit (events.js:188:7)
    at Pipe._handle.close [as _onclose] (net.js:498:12)

如果你只想记录错误的堆栈跟踪(而不是错误消息)，Node 6及以上会自动在堆栈跟踪中包含错误名称和消息，如果你想做一些自定义错误处理，这有点烦人:

console.log (error.stack.replace(错误。信息,”)

这个解决方案将只记录错误名称和堆栈跟踪(因此，例如，您可以格式化错误消息，并在代码中的其他地方以您希望的方式显示它)。

上面的例子只打印错误名称，后面跟着堆栈跟踪，例如:

Error: 
    at /Users/cfisher/Git/squashed/execProcess.js:6:17
    at ChildProcess.exithandler (child_process.js:213:5)
    at emitTwo (events.js:106:13)
    at ChildProcess.emit (events.js:191:7)
    at maybeClose (internal/child_process.js:877:16)
    at Socket.<anonymous> (internal/child_process.js:334:11)
    at emitOne (events.js:96:13)
    at Socket.emit (events.js:188:7)
    at Pipe._handle.close [as _onclose] (net.js:498:12)

而不是:

Error: Error: Command failed: sh ./commands/getBranchCommitCount.sh HEAD
git: 'rev-lists' is not a git command. See 'git --help'.

Did you mean this?
        rev-list

    at /Users/cfisher/Git/squashed/execProcess.js:6:17
    at ChildProcess.exithandler (child_process.js:213:5)
    at emitTwo (events.js:106:13)
    at ChildProcess.emit (events.js:191:7)
    at maybeClose (internal/child_process.js:877:16)
    at Socket.<anonymous> (internal/child_process.js:334:11)
    at emitOne (events.js:96:13)
    at Socket.emit (events.js:188:7)
    at Pipe._handle.close [as _onclose] (net.js:498:12)

如果有人还在寻找这个像我一样，那么有一个模块，我们可以使用称为“堆栈跟踪”。它真的很受欢迎。NPM链接

然后穿过痕迹。

  var stackTrace = require('stack-trace');
  .
  .
  .
  var trace = stackTrace.get();
  trace.map(function (item){ 
    console.log(new Date().toUTCString() + ' : ' +  item.toString() );  
  });

或者只是简单地打印跟踪:

var stackTrace = require('stack-trace');
.
.
.
var trace = stackTrace.get();
trace.toString();

在控制台以更易读的方式打印错误的堆栈跟踪:

console.log(ex, ex.stack.split("\n"));

结果示例:

[Error] [ 'Error',
  '    at repl:1:7',
  '    at REPLServer.self.eval (repl.js:110:21)',
  '    at Interface.<anonymous> (repl.js:239:12)',
  '    at Interface.EventEmitter.emit (events.js:95:17)',
  '    at Interface._onLine (readline.js:202:10)',
  '    at Interface._line (readline.js:531:8)',
  '    at Interface._ttyWrite (readline.js:760:14)',
  '    at ReadStream.onkeypress (readline.js:99:10)',
  '    at ReadStream.EventEmitter.emit (events.js:98:17)',
  '    at emitKey (readline.js:1095:12)' ]

据我所知，在nodejs中打印完整的堆栈跟踪是不可能的，你可以只打印“部分”堆栈跟踪，你无法看到你从代码中的哪里来，只是异常发生的地方。这就是瑞恩·达尔在youtube视频中解释的内容。http://youtu.be/jo_B4LTHi3I为了精确，至少56:30。希望这能有所帮助

尝试错误。captureStackTrace (constructorOpt targetObject[])。

const myObj = {};
function c() {
  // pass
}

function b() {
    Error.captureStackTrace(myObj)
    c()
} 

function a() {
    b()
}

a()

console.log(myObj.stack)

函数a和b在错误堆栈中被捕获并存储在myObj中。