React Repositories Are Leaving Facebook: What the Move to react/* Means for Developers

A change quietly happened in the React ecosystem recently, but its significance goes far beyond GitHub URLs.

For years, React developers have been accustomed to repositories living under the familiar facebook/* organization:

• facebook/react
• facebook/react-native
• facebook/metro
• facebook/yoga

Those URLs became part of everyday development. They appeared in documentation, conference talks, tutorials, issue trackers, and countless GitHub stars.

Now, that chapter is beginning to close.

React repositories are moving from:

facebook/ → react/

At first glance, this might seem like a simple organizational cleanup. GitHub redirects will continue to work, existing links won’t suddenly break, and most developers won’t need to change anything immediately.

But the move represents something much larger: the continued evolution of React from a Facebook-created framework into a community-governed open-source platform.

How React Got Here

When React was first open-sourced in 2013, it was very much a Facebook project.

The framework was developed internally to solve UI challenges at Facebook scale and was later released to the public. For many years, Facebook engineers led development, made major architectural decisions, and maintained the ecosystem.

During that period, the connection between React and Facebook was clear.

The repository lived under Facebook’s GitHub organization.

The website highlighted Facebook’s involvement.

Most major announcements came directly from Facebook engineering teams.

But React’s growth quickly surpassed its origins.

Today React powers:

• Startups
• Enterprise applications
• Government platforms
• Open-source projects
• Mobile applications through React Native
• Internal tools across thousands of companies

For millions of developers, React is no longer viewed as “Facebook’s framework.”

It’s simply React.

The Rise of the React Foundation

The repository migration aligns with the broader transition toward the React Foundation.

Open-source projects often reach a stage where governance expands beyond the company that originally created them.

We’ve seen similar patterns across the industry:

• Linux and the Linux Foundation
• Kubernetes and the Cloud Native Computing Foundation
• Node.js and the OpenJS Foundation
• Electron and community-led governance models

As projects become critical infrastructure for the software industry, long-term sustainability becomes increasingly important.

The React Foundation helps provide that structure.

Instead of React being perceived as a product owned entirely by a single company, it becomes a project guided with broader ecosystem participation and long-term stewardship in mind.

The new GitHub organization reflects that direction.

Which Repositories Are Moving?

The initial migration includes several key projects across the React ecosystem:

React

The core library that powers modern user interfaces.

React Native

The framework used to build native mobile applications with React.

Metro

The JavaScript bundler used by React Native.

Yoga

The cross-platform layout engine that powers React Native layouts.

React Strict DOM

An emerging project focused on web platform consistency.

React Native Website

Documentation and website resources for React Native.

Create React App

Although many teams have moved toward frameworks like Next.js and Expo, CRA remains an important historical part of the React ecosystem.

JSX

The syntax extension that fundamentally changed how many developers build UI.

React DevTools

The debugging tools used daily by React developers worldwide.

And this list may continue growing as additional repositories transition to the new organization.

What Changes for Developers?

The practical impact is surprisingly small.

GitHub automatically handles redirects for renamed repositories and organizations.

That means:

• Existing repository links continue working
• Existing Git remotes continue working
• Existing stars and watchers remain intact
• Open pull requests and issues remain available

For most teams, development workflows will continue exactly as before.

However, there are a few areas worth reviewing:

Documentation

Internal documentation may still reference old repository URLs.

CI/CD Scripts

Some automation scripts hardcode repository paths and should be reviewed.

Open Source Contributions

Contributors may start seeing the new repository URLs in issue references, discussions, and pull requests.

Developer Education Content

Tutorials, blog posts, and videos will gradually transition to the new organization names.

Why This Matters Symbolically

Technology communities pay attention to symbols because symbols often reveal future direction.

The move to react/* signals several things:

React Is Bigger Than One Company

While Meta remains a major contributor, React’s success comes from a global ecosystem of maintainers, educators, library authors, framework teams, and developers.

The new organization reflects that reality.

Community Confidence

Many organizations invest millions of dollars into React-based products.

A foundation-backed governance model can provide additional confidence that the ecosystem will remain stable for the long term.

Ecosystem Maturity

Projects typically make this kind of transition when they reach a certain level of maturity.

React is no longer a fast-growing experimental framework.

It has become foundational infrastructure for modern software development.

What About React.dev?

One interesting detail is that the React documentation website remains under its current setup for now.

A likely reason is the complexity of the documentation ecosystem itself.

The React documentation project relies on:

• Community contributions
• Translation efforts
• Internationalization workflows
• Numerous forks and mirrors

Migrating documentation infrastructure often requires significantly more coordination than moving source code repositories.

As a result, documentation-related projects may follow a different timeline than core repositories.

Looking Ahead

The GitHub organization migration is unlikely to be the last visible change resulting from the React Foundation’s growth.

As React continues evolving, we may see:

• More repositories moving under the React organization
• Expanded governance processes
• Increased community participation
• Stronger ecosystem collaboration
• Additional foundation-led initiatives

None of this changes how developers write React code tomorrow.

But it does change how the project is positioned for the next decade.

Final Thoughts

Most developers will barely notice this migration during their daily work.

Their applications will still compile.

Their Git commands will still work.

Their favorite React libraries will continue functioning exactly as before.

Yet this remains one of the most meaningful organizational shifts in React’s history.

For over a decade, React carried the identity of being a Facebook project.

Today, it is becoming something larger: a community-driven platform governed for the long-term health of one of the world’s most important open-source ecosystems.

The URL change may be small.

The message behind it is not.

Goodbye facebook/react.

Welcome react/react.