Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Stack traces for exceptions inside getInitialProps() show babel internals #5028

Closed
wilsonpage opened this issue Aug 25, 2018 · 1 comment
Closed

Stack traces for exceptions inside getInitialProps() show babel internals #5028

wilsonpage opened this issue Aug 25, 2018 · 1 comment

Comments

@wilsonpage
Copy link

Bug report

Describe the bug

When an exception is thrown inside a page's getInitialProps() the stack trace shows internal Babel regenerator-runtime code instead of recognisable app code. This make it hard to debug.

To Reproduce

Steps to reproduce the behavior, please provide code snippets or a repository:

  1. Throw an Error inside getInitialProps()
  2. See stack-trace like above.

Expected behavior

A stack trace that shows library and application code only, not transpiled code.

Screenshots

image

System information

  • Version of Next.js: 6.1.1
@timneutkens
Copy link
Member

timneutkens commented Aug 25, 2018 •
edited
Loading

Duplicate of #4613, please try next@canary (Next 7 beta) there's been quite some improvements on the stacktraces front.

@lock lock bot locked as resolved and limited conversation to collaborators Aug 25, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@wilsonpage @timneutkens