preactjs / preactjs/preact-devtools

Make best effort to detect remounts

Open
#169 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
TypeScript
Stars
345
Forks
39
PR merge metrics
No merged PRs in 30d

Description

Suggestion via slack:

One thing that also I’d love to know during debugging is if a certain compnent was remounted (aka now has new identity) or not. I’m trying to understand if by some reason my app does too many renders. Like maybe some sort of auto-incrementing id could work for me here. Maybe there’re better and more usable ways to do it, like showing unmounted components in the tree, but i dont know

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

The issue names no files, tests, or entry points. Start by tracing how the extension represents component identity and mount/unmount events, then decide how remounts should be surfaced in the component tree; done means a reliable, understandable remount signal is visible during debugging.

Written by the indexing model from the issue text.

Assessment

Tech stack
typescript
Domain
devtools
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.