You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The error page doesn't show when there is a runtime error.
The issue I had was importing gsap when it needed the next-transpile-modules package as currently Next.js is not supporting ES6 modules. When navigating to the page, the next dev server logs the following:
So the page builds ok, but immediately followed by the default error page. However, in browser, the request simply hangs and the page doesn't load. I don't see any error being displayed back to me or in console.
Expected Behavior
See error.
The problem can be worked around by creating a custom error page _error. Using documentation code:
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
locked as resolved and limited conversation to collaborators
Jan 27, 2022
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
What version of Next.js are you using?
11.0.1
What version of Node.js are you using?
15.2.1
What browser are you using?
Edge Chromium
What operating system are you using?
Windows
How are you deploying your application?
next dev
Describe the Bug
The error page doesn't show when there is a runtime error.
The issue I had was importing gsap when it needed the next-transpile-modules package as currently Next.js is not supporting ES6 modules. When navigating to the page, the next dev server logs the following:
So the page builds ok, but immediately followed by the default error page. However, in browser, the request simply hangs and the page doesn't load. I don't see any error being displayed back to me or in console.
Expected Behavior
See error.
The problem can be worked around by creating a custom error page _error. Using documentation code:
To Reproduce
without the following in next.config.js
The text was updated successfully, but these errors were encountered: