Error stack not exposed when axios error occurs inside `getInitialProps` function

Bug report

Error stack not exposed when axios error occurs inside getInitialProps function

Describe the bug

In the getInitialProps function, the error page is not displayed properly in client side rendering when an error occurs due to axios.

Page code

// pages/example.js
...
ExamplePage.getInitialProps = () => {
  // The code below throws a CORS error on the client side.
  await axios.get('https://google.com');
  ...
  return {}
}
...

Run script

// Run nextjs in development mode.
$ next dev

Expected behavior

If an error occurs in getInitialProps function when entering a page through next/route(route.push) on the client side, the error information should be exposed on the page, but if an axios error occurs, the error page is not exposed(As a result of testing, other errors except axios error are normally showing error information on the page.).

System information

• Browser Chrome
• Version of Next.js: 9.2.1

[rafaelalmeidatk]

This is a known problem with axios because it rewrites the stack trace. I wrote about a workaround here: https://github.com/rafaelalmeidatk/TIL/issues/4

[balazsorban44]

This issue has been automatically locked due to no recent activity. If you are running into a similar issue, please create a new issue with the steps to reproduce. Thank you.