devtools 7.7.7 on Firefox now only breaks in Vue components if "Pause on caught exceptions" is set
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 2.9k
- Forks
- 279
- PR merge metrics
- No merged PRs in 30d
Description
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?
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the behavior in Vue 3 components with Firefox's "Pause on exceptions" settings, then inspect Vue 3's internal logError path and the asynchronous update loop mentioned in the report. Done means the original throw location is reachable without requiring "Pause on caught exceptions" to stop on unrelated library errors.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- devtools, typescript
- Domain
- devtools, frontend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100