How to get the full Node.js stack trace when using async/await?

Question

Let's say I have 12 async/await functions, and on the 12th one deep, an error happens. Right now, I have this code to catch all errors:

process.on('unhandledRejection', function {
    console.error(err);
    process.exit(1);
});

The problem is, the stacktrace is not returned:

ReferenceError: sdfg is not defined
- get.js:29 Fruit.module.exports [as get]
  /project/models/fruit/get.js:29:2
- next_tick.js:129 process._tickDomainCallback
  internal/process/next_tick.js:129:7

On other projects, when I used callbacks with the structure of:

function doSomething(err, done) {
  if (err) { return done(err); }
  /* do something */
  return done(null, true);
}

Then I had a nice stack trace of where the error has occured and the steps that led there. Now with async/await I've tried catching errors at all kinds of levels with no result. I've also tried longjohn and stackup -- and I still get only the last function that threw the error.

Help -- how do I see the complete stack?! And what's the proper way to catch nested async/await errors?

EDIT: (a complete example)

const getA = async () => {
    await getB();
}

const getB = async () => {
    await getC();
    sdgf();
}

const getC = async () => {}

const start = async () => {
    await getA();
}

start().then().catch(e => console.error(e));

ralfstx · Accepted Answer · 2019-07-22 17:05:04Z

4

This issue appears to be resolved in Node 12. With v12.6.0, the snippet in the original post yields the following stack trace:

ReferenceError: sdgf is not defined
    at getB (/path/to/test.js:7:3)
    at async getA (/path/to/test.js:2:3)
    at async start (/path/to/test.js:15:3)

edited Jul 22, 2019 at 17:05

answered Jul 17, 2019 at 7:21

ralfstx

4,0732 gold badges30 silver badges42 bronze badges

Sign up to request clarification or add additional context in comments.

Comments

K. Norbert · Accepted Answer · 2018-09-26 14:33:48Z

2

It is not possible to get the stack trace after the first await statement, in an async function, as of today.

https://github.com/nodejs/node/issues/11865

answered Sep 26, 2018 at 14:33

K. Norbert

10.7k5 gold badges52 silver badges48 bronze badges

Comments

Josh Beam · Accepted Answer · 2017-04-10 16:51:22Z

1

unhandledRejection error handler might not be the right way to try to catch all these. I'd suggest wrapping your async/awaits in try/catch blocks:

async function doSomething() {
  try {
    await doSomethingElse()
  } catch(err) {
    console.log(err)
  }
}

This should give you a better stack trace.

answered Apr 10, 2017 at 16:51

Josh Beam

19.9k5 gold badges48 silver badges69 bronze badges

8 Comments

John Derring Over a year ago

This is what that gives: ReferenceError: sdfg is not defined at Fruit.module.exports [as get] (/models/fruit/get.js:29:2) at process._tickDomainCallback (internal/process/next_tick.js:129:7)

Josh Beam Over a year ago

@JohnDerring that looks like a stack trace, saying that sdfg is not defined at line 29 of the fruit model. What am I missing?

John Derring Over a year ago

The 11 other functions that came before getting to this function? In other words the complete stack trace...?

Josh Beam Over a year ago

@JohnDerring is the sdfg error happening on fruit/get.js line 29, or is it happening somewhere else?

John Derring Over a year ago

Yes, exactly. On fruit/get.js:29 I put a sdfg() just to throw an error, so that's the correct place. The problem is it takes 11 other async/await functions to get to this place, and the error stack is just showing 2 places: the fruit/get.js and the next_tick). I'm confused about how to show the complete error stack...

|

Collectives™ on Stack Overflow

How to get the full Node.js stack trace when using async/await?

3 Answers 3

Comments

Comments

8 Comments

Your Answer

Hot Network Questions

Collectives™ on Stack Overflow

3 Answers 3

Comments

Comments

8 Comments

Your Answer

Sign up or log in

Post as a guest

Related