Add support for async stack traces

[ErkoKnoll]

Starting from Node 12 it is possible to enable async stack traces which adds additional 'async' prefix part: https://thecodebarbarian.com/async-stack-traces-in-node-js-12

I think currently the parsing won't work properly if the stack trace contains 'async' prefix.

[Calamari]

Thanks for pointing to this new feature. I will check it out and see if we have to adapt things there.

[Calamari]

Finally got to it. No work needed here, but I added some more tests. Do you agree? Or do you see another case where it might go wrong?

[ErkoKnoll]

Your tests are indeed passing and I managed to find out why my case was failing. I was returning stack trace from V8 that had the file name set to script, to fix it I had to changed the file name into /script.js.

Since that workaround works for me you can close the issue, but I also wrote the test case for it if you are interested:

V8: {
    message: 'Oops',
    name: 'Error',
    stack:
      'Error: Oops\n' +
      '    at foo (script:22:11)\n' +
      '    at async bar (script:18:5)\n' +
      '    at async script:5:18'
  },

it('parses V8 async errors', () => {
    const stackFrames = stackTraceParser.parse(
      CapturedExceptions.V8.stack
    );
    expect(stackFrames.length).to.be(3);
    expect(stackFrames[0]).to.eql({
      file: 'script',
      methodName: 'foo',
      arguments: [],
      lineNumber: 22,
      column: 11,
    });
    expect(stackFrames[1]).to.eql({
      file: 'script',
      methodName: 'async bar',
      arguments: [],
      lineNumber: 18,
      column: 5,
    });
    expect(stackFrames[2]).to.eql({
      file: 'script',
      methodName: 'async',
      arguments: [],
      lineNumber: 5,
      column: 18,
    });
  });

[Calamari]

Thanks for the feedback, since this sounds like a valid thing that can happen, I think this should work as well.
Out of curiousity, how did you end up with a filename without a .js ending?

I think it might also be a problem when catching erros in the REPL, (also I think that case is a very, very, very rare edge case g).

[ErkoKnoll]

I'm interacting with V8 directly and I can assign file names separately from the actual content. But indeed, it's a very rare edge case that can be easily fixed.