# dai-shi/react-tracked

State usage tracking with Proxies. Optimize re-renders for useState/useReducer, React Redux, Zustand and others.

Repository: https://github.com/dai-shi/react-tracked
Canonical: https://ross.abutalabs.com/products/react-tracked
Homepage: https://react-tracked.js.org
Language: TypeScript
License: MIT
License Family: permissive
Topics: react, react-hooks, global-states, react-context, redux, zustand
Last push: 2026-05-19T15:22:43+00:00

## Health v2 (maintenance only)
Score: 70/100 (v2, computed 2026-09-02T17:46:02.011165+00:00)
- activity 83, release rhythm 35, longevity 100
- inputs: {"age_days": 2639, "days_push": 106, "days_rel": null, "gap_med": null, "n_releases_24m": 0}
- flags: no_releases
- formula: round(0.45*activity + 0.35*rhythm + 0.20*longevity); archived -> min(score, 10)

## Adoption (not part of the score)
Stars 2820, forks 70 (observed 2026-08-28T04:07:23.979762+00:00)

## What it is
React Tracked is a TypeScript library that provides state usage tracking using JavaScript Proxies to optimize React re-renders. It works with useState/useReducer, React Context, React Redux, Zustand, and other selector-based state libraries, re-rendering components only when accessed properties change.

## Use cases
- prevent unnecessary re-renders in react apps with global state
- replace react context for global state without performance issues
- track state property access with proxies instead of writing selectors
- optimize react-redux useSelector re-renders
- add usage tracking to zustand or other selector hooks
- manage deep nested global state in react components

## When to choose
- your react app has a central global state consumed by many components and suffers from re-render performance issues
- you want useContext-like ergonomics without its re-render behavior
- you find writing selectors for performance cumbersome or error-prone
- you want to wrap an existing useSelector hook with usage tracking

## When to avoid
- your app is small and re-renders are not a measurable performance problem
- you prefer explicit selectors or a full state management solution like Redux Toolkit or Zustand alone
- you need server-side state caching (e.g. React Query) rather than client global state
- you target environments without ES6 Proxy support

## Facets
- artifact type: library
- maturity: active
- function: state-management, frontend-framework
- domain: frontend, web-development, performance
- platform: browser, cross-platform
- tags: react, react-hooks, proxies, re-render-optimization, global-state, redux, zustand, react-context, typescript, nodejs

## Member repositories
- dai-shi/react-tracked (main) score 70

## Provenance
- Observed fields: from GitHub, fetched 2026-08-28T04:07:23.979762+00:00.
- Health v2: computed from the inputs above; adoption is never an input.
- Inferred fields (summary, facets, guidance): AI-extracted, prompt v1, taxonomy v1, on 2026-08-30T07:38:19.652024+00:00, confidence not recorded.
  - readme: https://github.com/dai-shi/react-tracked (fetched 2026-08-28T04:07:23.979762+00:00, sha 63607b68946b)
  - homepage: https://react-tracked.js.org (fetched 2026-08-29T09:53:59.700579+00:00, sha be37b0a3d268)
  - site_page: https://react-tracked.js.org/docs/introduction (fetched 2026-08-29T09:53:59.709401+00:00, sha dbc8ab8ed640)
  - site_page: https://react-tracked.js.org/docs/tutorial-01 (fetched 2026-08-29T09:53:59.711332+00:00, sha 851f3ac5d31b)
  - site_page: https://react-tracked.js.org/docs/api (fetched 2026-08-29T09:53:59.713566+00:00, sha 03f1fdc3d8fa)
  - registry_npm: https://registry.npmjs.org/react-tracked (fetched 2026-08-29T09:53:59.715864+00:00, sha 52fe479702e0)
- Data as of 2026-08-30T08:39:29.467469+00:00.