facebook/react

★ 244,834JavaScriptAudience · developerComplexity · 2/5LicenseSetup · easy

Mindmap

mindmap
  root((repo))
    Core ideas
      Declarative UI
      Component-based
      Learn once write anywhere
    How it works
      JSX syntax
      State and props
      Efficient DOM updates
    Targets
      Web browsers
      Server via Node
      Mobile via React Native
    License
      MIT
      Meta maintained

mindmap root((repo)) Core ideas Declarative UI Component-based Learn once write anywhere How it works JSX syntax State and props Efficient DOM updates Targets Web browsers Server via Node Mobile via React Native License MIT Meta maintained

Click or tap to explore — scroll the page freely

Things people build with this

USE CASE 1

Build interactive web interfaces by composing small, reusable components that each manage their own state.

USE CASE 2

Add a reactive UI layer to an existing web project without rewriting the whole stack.

USE CASE 3

Share UI logic between a web app and a mobile app via React and React Native from one codebase.

USE CASE 4

Render React components on the server with Node.js for faster initial page loads.

Tech stack

JavaScriptJSXReact Native

Getting it running

Difficulty · easy Time to first run · 30min

Requires Node.js, easiest to bootstrap a new project with Create React App or Vite.

Use, modify, and distribute freely for any purpose including commercial projects, as long as you keep the copyright notice, MIT licensed.

In plain English

React is a JavaScript library for building user interfaces, both for web and for native (mobile) apps. The README describes its core ideas in three points. First, it is declarative: instead of writing step-by-step instructions for updating the screen, you describe what each "view" should look like for a given application state, and React figures out which parts to update efficiently when the underlying data changes. The README argues this makes code more predictable and easier to debug. Second, it is component-based: you build small, encapsulated components that manage their own internal state, and you compose them together into more complex interfaces. Component logic is written in JavaScript rather than in separate template files. Third, the slogan "Learn Once, Write Anywhere" means React does not assume the rest of your technology stack, can be added gradually to an existing project, and can be rendered on the server with Node or used to power mobile apps via React Native. The way it works is that a developer writes components that return descriptions of UI, often using a syntax called JSX that looks like HTML embedded in JavaScript. The example in the README defines a HelloMessage component and uses createRoot from react-dom/client to render it into a container element on the page. JSX is not strictly required, but the README says it makes code more readable. Someone would use React when they need to build interactive web or mobile interfaces, when they want to gradually adopt a UI library inside an existing project, or when they want one programming model for both web and native apps. The repository's primary language is JavaScript and the project is MIT licensed.

Copy-paste prompts

Prompt 1

I'm building a to-do app in React for the first time. Show me how to create a component that holds a list of tasks in state and lets me add and remove items using hooks.

Prompt 2

I have an existing HTML and jQuery website. How do I gradually add React to just one section of the page without rewriting everything?

Prompt 3

Explain the difference between React state and props to a non-developer in plain English, using a real-world analogy.

Prompt 4

I want to render my React component on the server using Node.js. Show me the minimal example using renderToString or the newer streaming APIs.

Open on GitHub → Explain another repo

This repo across BitVibe Labs

Scan in gitsafehub Deploy in gitdeployhub facebook on gitmyhub

Verify against the repo before relying on details.