How to filter out certain components that are not being monitored and reduce lag
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 2.9k
- Forks
- 279
- PR merge metrics
- No merged PRs in 30d
Description
The reason is that we have designed some complex common components for internal use, which have no sensory performance issues when not using devtools. However, when debugging with devtools, it becomes particularly laggy. Is it possible that our component design is too complex? So I hope there can be a way to filter out the listening of some components, and when it is necessary to debug this component, manually turn on the listening before debugging.
Overall, we hope to have a way to configure components not to be monitored and reduce performance consumption.
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
No files or tests are named. Start by reproducing the lag while inspecting complex components with Vue Devtools, then trace how component monitoring is configured; done means users can exclude selected components and manually re-enable monitoring when needed.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- devtools, performance
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100