Discofork
Repository brief

facebook/create-react-app

Read the upstream summary on the left, browse the cached forks below it, and load each fork comparison into the right-hand panel.

Cached analysis
cached 2026-03-29T22:26:20.409Z
3mo ago

facebook/create-react-app

Create React App is a Node.js/JavaScript project for bootstrapping React apps with one command. The repository is now explicitly deprecated and in long-term stasis, with the README recommending migration to newer React frameworks rather than starting production apps on CRA. It is still a large, highly starred and highly forked repo, so its forks are mainly interesting for legacy maintenance, migrations, or studying the original scaffolding tool.

GitHub
Loading tags...
Stars103,800
Forks27,102
Default branchmain
Last pushed2025-02-15T01:32:11Z
Recommended shortcuts

Jump straight into Discofork's strongest cached fork picks, or open a compare view in one click.

Forks

Choose a fork to inspect

6 of 6 fork briefs
Selected

Choose this fork only if you need legacy CRA with custom config support and you already have a project built on it. For new work, the combination of CRA stasis and this fork’s stale update history makes it a poor default choice.

Choose this fork if you specifically want a zero-config Inferno starter and can live with slower maintenance. Avoid it if you want the current upstream CRA direction or are starting a new React production app.

Choose this fork if your target is a React browser extension and you value the extension templates more than upstream freshness. Avoid it for new general-purpose React apps or if you need current CRA behavior and active maintenance.

Choose this fork only if you need a frozen legacy CRA snapshot. If you want fixes, current guidance, or a path for new work, upstream or a modern React framework is the better choice.

Prefer this fork only if you are maintaining a legacy project that already depends on it or you specifically want its early convenience patches. For new work, the fork is too stale and too far behind upstream to be a safe default.

Choose this fork only if you specifically need CRA-style scaffolding adapted for Laravel projects. For new React work, upstream CRA is deprecated and this fork is stale enough that the maintenance burden and drift are likely the main tradeoff.