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.

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

Reference error: err is not defined #9430

Closed
vitorhsb opened this issue Nov 16, 2019 · 2 comments · Fixed by #9431
Closed

Reference error: err is not defined #9430

vitorhsb opened this issue Nov 16, 2019 · 2 comments · Fixed by #9431
Assignees
Milestone

Comments

@vitorhsb
Copy link
Contributor

vitorhsb commented Nov 16, 2019

Bug report

Describe the bug

Variable err is not defined, variable in catch is called error.

To Reproduce

Only found this error on a app deployed on Zeit Now with an api route with cors. In development it works.

Expected behavior

Catch error and log correctly, using error variable.

System information

  • Version of Next.js: 9.1.3

Additional context

Link to faulty code: https://github.com/zeit/next.js/blob/7c80febcf796c91bb776ea3b841cab18df221ff4/packages/next/build/webpack/loaders/next-serverless-loader.ts#L72

@ijjk
Copy link
Member

ijjk commented Nov 16, 2019

Hi, thanks for reporting this, it should be fixed in Next.js v9.1.4-canary.7

@Timer Timer added this to the 9.1.4 milestone Nov 16, 2019
@balazsorban44
Copy link
Member

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.

@vercel vercel locked as resolved and limited conversation to collaborators Jan 30, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

5 participants