node/test/fixtures/async-error.js
Joyee Cheung 757f3f8b2c
process: reduce the number of internal frames in async stack trace
Previously, we call the JS land `runNextTicks` implementation
immediately from JS land after evaluating the main module or the
input, so these synchronous JS call frames would show up in the stack
trace of the async errors, which can be confusing. This patch moves
those calls into C++ so that more of these internal scheduler
implementation details can be hidden and the users can see a cleaner
a cleaner async JS stack trace.

PR-URL: https://github.com/nodejs/node/pull/27392
Reviewed-By: Ruben Bridgewater <ruben@bridgewater.de>
Reviewed-By: Gus Caplan <me@gus.host>
Reviewed-By: Minwoo Jung <minwoo@nodesource.com>
Reviewed-By: Benjamin Gruenbaum <benjamingr@gmail.com>
2019-04-28 15:36:28 +08:00

28 lines
327 B
JavaScript

'use strict';
async function one() {
throw new Error('test');
}
async function breaker() {
return true;
}
async function stack() {
await breaker();
}
async function two() {
await stack();
await one();
}
async function three() {
await two();
}
async function four() {
await three();
}
module.exports = four;