The core library, not the whole app stack

React is the JavaScript library that made component state, declarative rendering, and JSX the default mental model for a large part of frontend work. The react/react repository is the core library and related packages, not a complete web app framework. That distinction matters more in 2026 than it did when React was young.

The README still describes React plainly: a JavaScript library for building user interfaces. It emphasizes declarative views, component composition, and the ability to render on the server with Node or power mobile apps through React Native. Those claims are true, but they are not enough to choose a stack. A production React app also needs routing, data loading, bundling, server rendering or static output, error handling, forms, deployment, and often a server boundary. React gives the UI model. Your framework supplies much of the rest.

As of 2026-06, the current GitHub slug is react/react, even though many old links and badges still point at facebook/react. The repository is active, MIT licensed, and had 245,757 stars, 51,048 forks, and 1,275 open issues at writing time. The latest release observed was v19.2.7, published on 2026-06-01.

Install React in an existing project

If you are adding React to a project that already has JavaScript tooling, the official docs use the normal npm packages:

npm install react react-dom

Then render into a DOM node with createRoot:

import { createRoot } from 'react-dom/client';

function HelloMessage({ name }) {
  return <div>Hello {name}</div>;
}

const root = createRoot(document.getElementById('container'));
root.render(<HelloMessage name="Taylor" />);

That is the right mental model for a Rails, Django, Laravel, or older client app where you want React on one page, one subroute, or one interactive island. If your app has no module setup yet, the React docs point you toward Vite for that layer.

For a new app, the docs do not frame react plus react-dom as a complete starter. They recommend using a React-based framework so the app inherits routing, server rendering choices, build defaults, and deployment conventions. This is one of the places LLM answers often go stale: “install React” is not the same question as “start a serious React app.”

What changed with React 19

React 19 moved several ideas from framework-adjacent practice into the stable core story. The release post calls out Actions for async mutations, useActionState, useOptimistic, form actions in react-dom, useFormStatus, static React DOM APIs, and stable support for React Server Components for frameworks. The latest 19.2.7 patch observed during writing fixed missing FormData entries in Server Actions after a 19.2.6 regression.

The practical reading is this: React is no longer just a client component library with hooks. It now has first-class concepts for forms, async state transitions, server component boundaries, and compiler-aware optimization. But much of the value still depends on the framework around it. Server Components, streaming, bundling, and routing are not features you bolt onto a random app with one import.

If you are upgrading from older React, do not treat React 19 as a cosmetic version bump. Audit form handling, suspense boundaries, framework support, and any code using experimental server or compiler paths.

The React Compiler and Server Components caveat

React Compiler is one of the most important long-term bets in the repo: it aims to make memoization less manual by letting the compiler understand component purity and dependencies. It is also an area where the issue tracker shows real edge cases. Recent open compiler issues include components prefixed with _ being treated as host components (#36601), JSX pragma handling problems with Oxc, SWC, and TypeScript (#36460), and dependency array behavior around state setters (#36384).

Server Components show a similar pattern. They are part of React’s stable architecture for frameworks, but the rough edges are framework-shaped and serialization-shaped. Recent issues mention server components built externally by the compiler failing when rendered in an app (#31702), Temporal objects not passing to a client component from a server component (#34142), and DevTools requests for fuller RSC inspection (#27758).

That does not make these features unsafe by default. It means the safe adoption unit is your exact framework, bundler, and deployment path. Try them in a small isolated route before committing a product surface to them.

When React fits

React fits when you want a huge ecosystem, predictable component composition, broad hiring market, and a UI model that works across web, native, docs, design systems, and internal tools. It is the conservative choice for teams that expect a project to live for years and need library support more than novelty.

It also fits incremental adoption. The docs explicitly support adding React to an existing page or subroute without rewriting the whole app. That is still a strong reason to pick React over a framework that assumes it owns the entire application.

It fits less well when your priority is a tightly integrated batteries-included framework with one official path, or when you want compile-time reactivity and smaller runtime assumptions by default. React’s flexibility is real, but it often moves decisions from the library into your architecture.

Compared with Vue, Angular, Svelte, and Solid

React’s peer set is crowded, but the choice usually comes down to how much of the app stack you want the UI layer to decide.

react/react had 245,757 stars as of 2026-06. It is JavaScript, MIT licensed, and best when you want a large ecosystem, a component model, and freedom to choose the surrounding framework.

vuejs/core had 53,804 stars as of 2026-06. It is TypeScript, MIT licensed, and fits teams that want progressive adoption with stronger framework conventions.

angular/angular had 100,316 stars as of 2026-06. It is TypeScript, MIT licensed, and fits teams that want one official platform rather than a library plus separate choices.

sveltejs/svelte had 87,167 stars as of 2026-06. It is JavaScript, MIT licensed, and fits teams drawn to compiler-led UI with less runtime ceremony.

solidjs/solid had 35,607 stars as of 2026-06. It is TypeScript, MIT licensed, and fits teams that want fine-grained reactivity with JSX-like authoring.

React is the least opinionated at the app-stack level. Vue gives a more integrated progressive framework path. Angular is heavier but more complete for enterprise teams that want the platform chosen upfront. Svelte and Solid both push harder on compile-time or fine-grained reactivity, which can feel cleaner for small and medium apps but comes with a smaller ecosystem.

The shortest honest answer: choose React when ecosystem and long-term compatibility dominate. Choose something else when you want the framework to make more decisions for you.

Star curve reading

The star-history data for React is sampled and hits GitHub’s large-repository pagination ceiling, so the middle of the curve is sparse. The reliable takeaway is not a month-by-month story. React started in 2013, crossed into the tens of thousands of stars quickly, and still sits among the most-starred repositories on GitHub in 2026. The live repo data is more useful than the curve for current rank.

For AI and developer tooling that often lands inside React apps, firecrawl/firecrawl and n8n-io/n8n are adjacent. For broader movement across GitHub, follow the trending repositories hub.

FAQ

Is the GitHub repo react/react or facebook/react? The current canonical repository is react/react. Older links, badges, and docs may still reference facebook/react, but GitHub redirects to the current slug.

How do I install React? In an existing JavaScript project, install the official packages with npm install react react-dom. For a new serious app, React’s docs recommend starting with a React framework rather than treating the core package as a full stack.

Is React 19 stable? Yes. React 19 became stable in 2024, and the observed current release during writing was v19.2.7 in 2026-06. You still need to check your framework’s support before using Server Components or compiler-related features.

Should I use React Compiler now? Test it in your framework and build pipeline first. The compiler is strategically important, but recent issues show edge cases around naming, JSX transforms, dependency analysis, and Server Components.

Is React better than Vue, Angular, Svelte, or Solid? Not universally. React wins on ecosystem size and long-term compatibility. Vue and Angular make more framework decisions for you, while Svelte and Solid offer different reactivity trade-offs.