remix-run/react-router

Prefer upstream unless you specifically need this fork's custom middleware/prerender/client-data/RSC work and are prepared to own a large rebase burden. For most adopters, the staleness and divergence outweigh the benefits.

Choose this fork only if you need its custom routing/workflow changes and are prepared to own the divergence. If you want the current React Router ecosystem, upstream is the safer choice.

Prefer this fork only if you need its custom routing/runtime changes and are prepared to maintain a long-lived divergence. If you want the safest path, upstream is the better choice because this fork is materially stale and likely missing a large amount of recent work.

Prefer this fork only if you need its specific client-data, prerender, or router-internals behavior and are willing to own a large divergence from upstream. If you want ongoing compatibility, current docs, and active maintenance, upstream is the better default.

Choose this fork only if you need its custom routing/tooling behavior and can afford to own a large divergence. If your priority is staying close to upstream React Router, this fork is a poor fit.

Choose this fork only if you must preserve an old React Router codebase and can accept being years behind upstream. For new work or active maintenance, upstream React Router is the better default.

Choose this fork only if you need legacy React Router behavior or old-version documentation. For new work, the active upstream is the better choice because this fork is far behind, stale, and missing the modern package and framework surface.

Choose this fork only if you are maintaining an older app that depends on legacy React Router behavior or a bundled UMD build. For new work, or if you want current React Router features and active maintenance, upstream is the better choice.