reactjs/rfcs resource
RFCs for changes to React observed · 2026-08-28
Health v2 · maintenance only
32/100
- Activity 0
- Release rhythm 35
- Longevity 100
Flags: no_releases
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: 3192
- days_rel: n/a
- days_push: 813
- n_releases_24m: 0
Adoption not part of the score
5807 stars · 572 forks observed · 2026-08-28
What it is AI-extracted, prompt v1, taxonomy v1, 2026-08-29, confidence not recorded
The official repository of Request for Comments (RFC) documents for the React project, where substantial changes and new features are proposed, discussed, and reviewed. It serves as a public record of React's design process and the rationale behind its API evolution.
Use cases
- understand why React features were designed the way they were
- track upcoming proposed changes to React
- learn how the React RFC process works before submitting a proposal
- research the history and rationale behind React APIs like hooks or server components
- find active React proposals open for community feedback
When to choose
- you want insight into the design rationale behind React features
- you are considering proposing a substantial change to React
- you want to preview experimental or upcoming React APIs
When to avoid
- you need React itself to build an application
- you want documentation for released React features rather than proposals
- you need a general-purpose RFC tool for your own project
Facets
learning-resource · maturity active
documentation web-development frontend documentation rfc react design-process community-governance specifications web-server
1 source
- readme: https://github.com/reactjs/rfcs · fetched 2026-08-28 · 6b5199c6a1a6
Member repositories
| Repository | Role | Health v2 |
|---|---|---|
| reactjs/rfcs | main | 32 |
For agents
Data as of 2026-08-30T08:39:29.467469+00:00 · Report a problem