garbles/why-did-you-update
:boom: Puts your console on blast when React is making unnecessary updates. observed · 2026-08-28
Health v2 · maintenance only
10/100
- Activity 0
- Release rhythm 35
- Longevity 100
Flags: no_releases archived no_license
How is this computed?
round(0.45*activity + 0.35*rhythm + 0.20*longevity); archived -> min(score, 10) — computed 2026-09-02. Adoption (stars, forks) is never an input.
- gap_med: n/a
- age_days: 3765
- days_rel: n/a
- days_push: 3266
- n_releases_24m: 0
Adoption not part of the score
4929 stars · 79 forks observed · 2026-08-28
What it is AI-extracted, prompt v1, taxonomy v1, 2026-08-29, confidence not recorded
A React library that logs to the console whenever a component re-renders unnecessarily, helping developers diagnose wasted renders. It is no longer maintained, with an actively maintained fork available.
Use cases
- find unnecessary React re-renders
- debug why my React component is re-rendering
- optimize React app performance
- detect wasted renders in React components
- profile React component update behavior
When to choose
- debugging wasted renders in an older React codebase
- quickly spotting components that re-render without prop changes
When to avoid
- new projects - use the maintained fork or React DevTools Profiler instead
- modern React versions where the tool may be incompatible
Facets
library · maturity abandoned
monitoring developer-tools logging frontend web-development developer-tools performance browser react debugging unnecessary-renders performance-profiling unmaintained nodejs javascript
1 source
- readme: https://github.com/garbles/why-did-you-update · fetched 2026-08-28 · 406d0a3ab379
Member repositories
| Repository | Role | Health v2 |
|---|---|---|
| garbles/why-did-you-update | main | 10 |
For agents
markdown · JSON · MCP: product_card(name="garbles/why-did-you-update")
Data as of 2026-08-30T08:39:29.467469+00:00 · Report a problem