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
Is it possible to get better source maps working? Currently console errors appear to be formatted such as:
dashboard.js:formatted:69368 Uncaught (in promise) TypeError: e.on is not a function
at dashboard.js:formatted:69368
at new Promise ()
at e.exports (dashboard.js:formatted:69367)
at dashboard.js:formatted:18424
at x (dashboard.js:formatted:26180)
at Generator._invoke (dashboard.js:formatted:26158)
at Generator.e. [as next] (dashboard.js:formatted:26195)
at n (dashboard.js:formatted:9199)
at s (dashboard.js:formatted:9213)
(anonymous) @ dashboard.js:formatted:69368
e.exports @ dashboard.js:formatted:69367
(anonymous) @ dashboard.js:formatted:18424
x @ dashboard.js:formatted:26180
(anonymous) @ dashboard.js:formatted:26158
e. @ dashboard.js:formatted:26195
n @ dashboard.js:formatted:9199
s @ dashboard.js:formatted:9213
It would be nice if the stack trace referred to the source file, rather than the build file. I believe this can be accomplished with webpack.
The text was updated successfully, but these errors were encountered:
Is it possible to get better source maps working? Currently console errors appear to be formatted such as:
It would be nice if the stack trace referred to the source file, rather than the build file. I believe this can be accomplished with webpack.
The text was updated successfully, but these errors were encountered: