Skip to content

Add react-debugger DevTools extension#157

Open
hoainho wants to merge 2 commits into
ChromeDevTools:masterfrom
hoainho:add-react-debugger
Open

Add react-debugger DevTools extension#157
hoainho wants to merge 2 commits into
ChromeDevTools:masterfrom
hoainho:add-react-debugger

Conversation

@hoainho
Copy link
Copy Markdown

@hoainho hoainho commented Feb 8, 2026

A Chrome DevTools extension for deep React debugging—profiling renders, detecting memory leaks, and surfacing anti‑patterns.

  • Performance profiling: render count, duration, and re‑render causes
  • Memory monitoring: heap usage + growth rate to spot leaks
  • Anti‑pattern detection: direct mutation, missing keys/deps, stale closures
  • Side Effects & CLS: analyze useEffect issues and layout shifts
  • Redux tooling: inspect state tree, time‑travel, and live state edits

@google-cla
Copy link
Copy Markdown

google-cla Bot commented Feb 8, 2026

Thanks for your pull request! It looks like this may be your first contribution to a Google open source project. Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).

View this failed invocation of the CLA check for more information.

For the most up to date status, view the checks section at the bottom of the pull request.

@hoainho
Copy link
Copy Markdown
Author

hoainho commented Feb 9, 2026

Thanks for your pull request! It looks like this may be your first contribution to a Google open source project. Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).

View this failed invocation of the CLA check for more information.

For the most up to date status, view the checks section at the bottom of the pull request.

I've signed a CLA, how I can re-trigger the CI to verify?

Comment thread readme.md
@hoainho
Copy link
Copy Markdown
Author

hoainho commented May 29, 2026

@merchandisesales144-cmd Review new commit again and give me an approve if its ok

@hoainho
Copy link
Copy Markdown
Author

hoainho commented May 31, 2026

Hi maintainers — gentle ping on this PR.

The CLA bot's last run was 2026-05-19 and shows FAILURE. I've signed the Google CLA twice (Feb 2026 and again May 2026 just to be safe). Could someone re-run the cla/google check, or let me know what additional step is needed?

Project status update since the original PR (Feb 2026):

  • v2.0.3 shipped Feb 28, 2026 with a major perf overhaul (sub-2ms-per-commit budget, hybrid render snapshot architecture, no host-page jank).
  • Active development: ongoing maintainer-led roadmap through Dec 2026 (self-roadmap, 8 new detectors planned).
  • Growing community: 12 stars, 7 forks, 21 open issues (10 good-first-issue), Wiki + Discussions live.
  • MIT licensed, CI green, has CONTRIBUTING.md, SECURITY.md, CODE_OF_CONDUCT.md.

Happy to update the PR description, rebase on current master, or split the change if any of that helps. Thanks for maintaining the list!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants