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
In previous versions of devtools for Vue 2 on Firefox, thrown errors in Vue components and supporting libraries would enter the debugger at the point of error if "Pause on exceptions" was set and "Pause on caught exceptions" was not. In 7.7.7 for Vue 3, if "Pause on caught exceptions" is not set, the error is handled by Vue 3's internal logError function and thrown from there; but the location where the error was thrown from is deep in the asynchronous update loop and there's no way to climb the stack to get to the location where the error is actually being thrown from. However, if "Pause on caught exceptions is set, I have to tread through a ton of extraneous errors, because many public libraries (e.g., lodash) throw and catch exceptions as part of their normal operation, but as a developer I am not interested in these exceptions. Is there any way to fix this?