我目前正在使用'request-promise'库来处理来自node-js的API调用,并努力从'catch'函数中获取正确的调用堆栈 . 在玩了一下之后,我注意到了一个我无法解释的有趣行为 . 说我有代码:
.catch(err => {
console.log(err.stack);
console.log('!!!');
console.log(new Error().stack);
});
在控制台中,我实际上看到了'err'和'new Error()'的两个完全不同的堆栈跟踪:
StatusCodeError: 404 - [object Object]
at new StatusCodeError (C:\MyProject\request-promise\lib\errors.js:26:15)
at Request.RP$callback [as _callback] (C:\MyProject\request-promise\lib\rp.js:68:32)
at Request.self.callback (C:\MyProject\request-promise\node_modules\request\request.js:187:22)
at Request.emit (events.js:110:17)
at Request.<anonymous> (C:\MyProject\request-promise\node_modules\request\request.js:1048:10)
at Request.emit (events.js:107:17)
at IncomingMessage.<anonymous> (C:\MyProject\request-promise\node_modules\request\request.js:969:12)
at IncomingMessage.emit (events.js:129:20)
at _stream_readable.js:908:16
at process._tickCallback (node.js:355:11)
!!!
Error
at C:/MyProject/src/server/controllers/bookingController.js:81:19
at tryCatcher (C:\MyProject\request-promise\node_modules\bluebird\js\main\util.js:26:23)
at Promise._settlePromiseFromHandler (C:\MyProject\request-promise\node_modules\bluebird\js\main\promise.js:510:31)
at Promise._settlePromiseAt (C:\MyProject\request-promise\node_modules\bluebird\js\main\promise.js:584:18)
at Promise._settlePromises (C:\MyProject\request-promise\node_modules\bluebird\js\main\promise.js:700:14)
at Async._drainQueue (C:\MyProject\request-promise\node_modules\bluebird\js\main\async.js:123:16)
at Async._drainQueues (C:\MyProject\request-promise\node_modules\bluebird\js\main\async.js:133:10)
at Immediate.Async.drainQueues [as _onImmediate] (C:\MyProject\request-promise\node_modules\bluebird\js\main\async.js:15:14)
at processImmediate [as _immediateCallback] (timers.js:367:17)
正如您所看到的,'new Error()'提供了有关调用堆栈的更多有用信息,因为它具有
'C:/MyProject/src/server/controllers/bookingController.js'
我想这是因为'错误'异常是用前一个勾号创建的,因此它的堆栈跟踪与我的'bookingController.js'无关 .
另外,我看到'request-promise'内部使用'bluebird',所以从技术上讲我可以使用Promise.longStackTraces() .
最后,我的问题是:有没有更聪明的方法来获得正确的堆栈跟踪,除了使用'new Error() . stack'技巧,因为Promise.longStackTraces()对于 生产环境 而言过于繁重?
1 回答
那么,nodejs提供了一个更漂亮的方法来捕获nodeJS上的实际堆栈,这符合我的需求: