Currently when passing errors to Stackdriver our error logs don't include a full stack trace as we use async/await pretty heavily in our system. This is partly a core issue with how Node handles async errors (see nodejs/node#11865 for details and a discussion on that) but it does hamper the utility of this library; even if this isn't something that can be resolved in this specific library having some guidance on how to improve async stack traces in the README would be nice.

Environment details

• OS: Node Alpine container distribution
• Node.js version: 9.4
• npm version: 5.6.0
• @google-cloud/error-reporting version: 0.1.3 (would update to the latest version but there's no obvious changelog anywhere and that makes me nervous without further exploration of the actual commit history)

Steps to reproduce

1. Create two async functions
2. Call one function from the other
3. Throw an error in the called function
4. Catch that error and log it using this library; alternatively, examine the stack trace in a non-debugger context