Inspecting state of components within RouterView stops working after some time
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 2.9k
- Forks
- 279
- PR merge metrics
- No merged PRs in 30d
Description
Since this week inspecting my vue components within a RouterView (vue-router) stops working after some time
Its very unexpectedly and I can't trace a pattern on how to resolve it or how to trigger it.
The only visible part while inspecting the components is the selected component outside the RouterView, but clicking on components inside the RouterView doesn't update anything besides the component name near the 'Filter State... input'
Every now and then i can access items inside the RouterView but it stops working overtime, refreshing the page doesn't help. reloading the frame doesn't help and reinstalling the extension doesn't help either.
The components do show on the left side under the 'Find components...' field so that's still working
Inspecting the devtools resulted in me finding this error:
devtools-panel.js:71 Uncaught (in promise) RangeError: Maximum call stack size exceeded
My versions:
Vue Router: tested on V4.4.0 and V.4.5.0 (latest)
Chrome Version: 131.0.6778.70
Vue.js devtools Version: 7.7.0
Vue Version: v3.4.38
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 issue with Vue Router 4.4.0 or 4.5.0 in Chrome and inspect the error at devtools-panel.js:71. Compare component inspection inside and outside RouterView, and determine whether the call-stack overflow can be reproduced. Done means RouterView components remain selectable and the RangeError no longer occurs.
Written by the indexing model from the issue text.
Assessment
- Domain
- devtools
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100