reactjs /rfcs

RFCs for changes to React

★ 5,818⑂ 569👁 555⑃ 171● 105▤ 0
MITCreated 2017-12-06
More from this author
-1
Daily
5,818
stars
569
forks
555
watchers
171
prs
105
issues
0
releases

README

React RFCs

Many changes, including bug fixes and documentation improvements can be
implemented and reviewed via the normal GitHub pull request workflow.

Some changes though are "substantial", and we ask that these be put
through a bit of a design process and produce a consensus among the React
core team.

The "RFC" (request for comments) process is intended to provide a
consistent and controlled path for new features to enter the project.

Active RFC List


 Contributor License Agreement (CLA)

In order to accept your pull request, we need you to submit a CLA. You only need
to do this once, so if you've done this for another Facebook open source
project, you're good to go. If you are submitting a pull request for the first
time, just let us know that you have completed the CLA and we can cross-check
with your GitHub username.

Complete your CLA here.

 When to follow this process

You should consider using this process if you intend to make "substantial"
changes to React or its documentation. Some examples that would benefit
from an RFC are:

  - A new feature that creates new API surface area, and would
     require a feature flag if introduced.
  - The removal of features that already shipped as part of the release
     channel.
  - The introduction of new idiomatic usage or conventions, even if they
     do not include code changes to React itself.

Some changes do not require an RFC:

  - Rephrasing, reorganizing or refactoring
  - Addition or removal of warnings
  - Additions that strictly improve objective, numerical quality
  criteria (speedup, better browser support)
  - Additions only likely to be _noticed by_ other implementors-of-React,
  invisible to users-of-React.

 What to expect

It is hard to write an RFC that would get accepted. Nevertheless, this shouldn't
discourage you from writing one.

React has a very limited API surface area, and each feature needs to work seamlessly with all other features.
Even among the team members who work on React full time every day, ramping up
and gaining enough context to write a good RFC takes more than a year.

In practice, React RFCs serve two purposes:

 React Team RFCs are submitted by React Team members after extensive (sometimes,
multi-month or multi-year) design, discussion, and experimentation. In practice, they comprise the
majority of the RFCs that got merged so far. The purpose of these RFCs is to preview the design
for the community and to provide an opportunity for feedback. We read every comment on the RFCs
we publish, respond to questions, and sometimes incorporate the feedback into the proposal.
Since our time is limited, we don't tend to write an RFC for a React feature unless we're very
confident that it fits the design. Although it might look like most React Team RFCs easily
get accepted, in practice it's because 98% of ideas were left on the cutting room floor. The remaining
2% that we feel very confident and

Top issues

Snapshot: 2026-11-16T09:23:14Z · Data license Apache-2.0 · JSON