🚀 v2.0.3 launch day — we are posting on Hacker News + dev.to + TWIR today

[hoainho]

🚀 v2.0.3 is out — and we're launching on Hacker News today

Hi everyone — short note for new visitors who just discovered the project (welcome 👋):

TL;DR: v2.0.3 shipped a major performance overhaul. Render detection is now aligned with @aidenbai's bippy engine (powering react-scan), host-page jank is eliminated, and the scan overlay fires synchronously at commit time.

What's new in v2.0.3

• Eliminated host-page jank — webNavigation.onCommitted filters by transitionType; heavy init deferred to idle callback
• Hybrid render snapshot architecture — 2ms budget on commit + deferred analysis via requestIdleCallback
• Accurate render detection — rewrote didFiberRender to use React's PerformedWork flag (0x01) as primary signal, eliminating false positives
• Synchronous scan overlay at commit time — immediate visual feedback (green ×1 → red ×10+)

Full release notes →

What is React Debugger?

The only Chrome extension that unifies React Timeline + Performance + Memory + Side Effects + Redux + CLS + AI analysis into a single DevTools tab — zero install in your app.

The defensible wedge: CLS overlay + useEffect audit + AI analysis — no other tool combines these three in one zero-install panel.

• It's not a replacement for React DevTools — install alongside
• It's not a replacement for react-scan — react-scan has the prettier in-page overlay; this is the Chrome extension with all the other tabs
• It's not a replacement for Redux DevTools — but you no longer need a separate extension if Redux is your only state library

Read the comparison table →

How to get involved

If the project resonates with you:

1. ⭐ Star the repo — every star helps more developers discover this work and signals that it matters
2. 👀 Watch releases — get notified when the MCP server (v2.1) and the next detector tabs ship
3. 🛠️ Pick a good-first-issue — 12+ open right now, all triage-ready, soft-claim policy explained in CONTRIBUTING.md
4. 💬 Share your debugging horror story in Q&A — the v2.1 roadmap is built from real bug-hunt stories
5. 📝 Write a blog post about the tool — Issue #14 is open and rewards the author with maintainer co-promotion

Where else we're posting today

• 🟧 Hacker News Show HN — happening today, link will be in replies once posted
• 📰 dev.to + Hashnode — long-form "I unified 7 React debugging tools into one panel" article
• 🐦 Twitter/X — 5-tweet thread with the demo GIF
• 💬 TWIR Discord #links — submission for the next This Week In React newsletter

If you found this project from one of those channels, thanks for clicking through — would love to hear what made you curious (or skeptical). Drop a comment below.

— Nho (@hoainho)

[hoainho]

Quick 3-day status update for anyone watching this thread — the HN/Reddit/Twitter posts slipped a few days (apologies, I had to deal with some contributor workflow bugs and a security follow-up first), but everything is on track for this weekend. Here's what changed since the original post:

What's new

• 🆕 Listed on up-for-grabs.net (5,965-star "beginner-friendly projects" index). That's a meaningful distribution channel for new contributors — expect a small but steady trickle of good first issue claims in the next few weeks.
• 🆕 First outside contribution in flight — @AsifpMulla123 opened PR fix(cli): route bootstrap installation logs to stderr to prevent MCP stream pollution #55 fixing a Windows-specific stdout leak in the CLI that was breaking the MCP JSON-RPC stream (issue [Bug]: CLI bootstrap leaks initialization diagnostic logs to stdout on Windows #49). High-quality root-cause diagnosis + fix in the issue itself. This is exactly the kind of contributor I was hoping the launch would attract.
• 🆕 Second contribution in flight — @iMindCap (a returning contributor from feat: improve MCPPairingPanel error messages for invalid token/port (#7) #17) is now working on a security follow-up: moving the MCP pairing token from chrome.storage.local to chrome.storage.session (issue [Security follow-up C-1] Move MCP pairing token from chrome.storage.local to .session #42). I'll be reviewing line-by-line on that one.
• 🆕 CI hardening — found and fixed a real bug in our Star Check workflow that was false-positive-failing first-time contributors (fix(ci): Star Check resilient to read-replica lag (fixes #55 false positive) #56). The fix adds 3-retry exponential backoff to absorb GitHub's read-replica lag.
• ⭐ 14 → 15 stars (the +1 is @AsifpMulla123 — first new stargazer this week)

What still needs to happen

The launch package is fully drafted (.sisyphus/growth/LAUNCH-NOW.md in the repo). Firing order will be:

1. Sat 2026-06-07 — Show HN first (HN ranking depends on early comment velocity)
2. Sat 2026-06-07 — Reddit r/SideProject + r/coolgithubprojects + r/chromeextensions
3. Sat 2026-06-07 — Twitter/X 5-tweet thread
4. Sun 2026-06-08 — dev.to article + Hashnode cross-post
5. Sun 2026-06-08 — TWIR Discord #links post

If the HN Show fires cleanly, the next 48h will be the bottleneck — I'm committing to reply to every comment within 15 minutes for the first 2 hours. If you find a bug while testing, open an issue with your username and I'll thank you publicly in the thread.

Thanks for your patience — and to anyone who starred in the last 3 days, the launch will be worth the wait. 🙏