reactjs/rfcs

This repository is the official home for RFCs (Requests for Comments) related to the React JavaScript library. When someone wants to propose a significant change to React, such as a new API, the removal of an existing feature, or a shift in how React applications are conventionally structured, they submit an RFC here as a pull request containing a written design document. The goal is to give proposed changes a structured path through discussion and review before any code is written. The README distinguishes two types of RFCs. React Team RFCs come from the people who maintain React itself. These are typically submitted at the end of a long design process, sometimes spanning months or years of internal discussion. They represent a high degree of confidence from the core team, and the majority of merged RFCs fall into this category. Community RFCs can be submitted by anyone, but most do not get accepted. The README is candid about this: rejection usually happens because a proposal has design gaps, conflicts with other React features, or falls outside the project scope. Even when a community RFC is not accepted, the discussion it generates can be valuable. Library authors, React team members, and other contributors read RFC threads when working on related problems, so a rejected RFC can still shape what eventually lands in the framework. The workflow itself is straightforward. You fork the repo, copy the template file, fill in your proposal, and open a pull request. Reviewers give feedback, the author revises, and if the core team agrees the proposal is a good fit, it enters a three-day final comment period before being merged. A merged RFC is called active, which means the team agrees in principle, not that someone is necessarily working on it or that it will ship in the next release. This is a governance and design repository, not a code library. There is nothing to install or run here.