-
Notifications
You must be signed in to change notification settings - Fork 27.3k
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
Better Stack Traces umbrella thread #4613
Comments
This one is actually fixed when React is upgraded, i believe 16.3 or 16.4 |
23 tasks
Note that Sergio's component is not just "the render of a component" it's inside a |
rauchg recently verified these in front. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Opening this issue to keep track of the different scenarios where we render unhelpful error messages
When I perform a navigation and the new page contains an error, we see a stack trace that references "hot-update" and other inaccessible locations
After a while, without taking action, one of our dynamic components shows a stacktrace that forces us to refresh:
undefined
componentIn this case I imported a component that wasn't properly exported (as
default
). The strangest of errors resulted:TypeError: Cannot read property 'toLowerCase' of undefined
at ReactDOMServerRenderer.renderDOM (/Users/rauchg/Projects/front/node_modules/react-dom/cjs/react-dom-server.node.development.js:2287:28)
at ReactDOMServerRenderer.render (/Users/rauchg/Projects/front/node_modules/react-dom/cjs/react-dom-server.node.development.js:2281:21)
at ReactDOMServerRenderer.read (/Users/rauchg/Projects/front/node_modules/react-dom/cjs/react-dom-server.node.development.js:2217:19)
at renderToString (/Users/rauchg/Projects/front/node_modules/react-dom/cjs/react-dom-server.node.development.js:2484:25)
at renderPage (/Users/rauchg/Projects/front/node_modules/next/dist/server/render.js:275:26)
at Function.getInitialProps (/Users/rauchg/Projects/front/node_modules/next/dist/server/document.js:67:25)
at _callee$ (/Users/rauchg/Projects/front/node_modules/next/dist/lib/utils.js:111:30)
at tryCatch (/Users/rauchg/Projects/front/node_modules/regenerator-runtime/runtime.js:62:40)
at Generator.invoke [as _invoke] (/Users/rauchg/Projects/front/node_modules/regenerator-runtime/runtime.js:296:22)
at Generator.prototype.(anonymous function) [as next] (/Users/rauchg/Projects/front/node_modules/regenerator-runtime/runtime.js:114:21)
at step (/Users/rauchg/Projects/front/node_modules/@babel/runtime/helpers/asyncToGenerator.js:12:30)
at _next (/Users/rauchg/Projects/front/node_modules/@babel/runtime/helpers/asyncToGenerator.js:27:9)
at /Users/rauchg/Projects/front/node_modules/@babel/runtime/helpers/asyncToGenerator.js:34:7
at new Promise ()
at new F (/Users/rauchg/Projects/front/node_modules/core-js/library/modules/_export.js:36:28)
at /Users/rauchg/Projects/front/node_modules/@babel/runtime/helpers/asyncToGenerator.js:7:12
The text was updated successfully, but these errors were encountered: