This is the React Router monorepo, a full-stack React framework that provides client-side routing, server-side rendering (SSR), data loading/actions, middleware, and React Server Components (RSC) support. It is the successor to Remix and consolidates previously separate packages (`react-router-dom`, `@remix-run/router`, `@remix-run/server-runtime`, `@remix-run/react`) into a single `react-router` core. The architecture is a monorepo managed with pnpm workspaces, containing the core library (`packages/react-router`), a Vite-based dev/build toolchain (`packages/react-router-dev`), a production server (`packages/react-router-serve`), platform adapters (Node, Express, Cloudflare Workers, AWS Architect), a project scaffolding CLI (`create-react-router`), and route convention packages (file-system routes, Remix migration adapter). Key entry points include the `RouterProvider`/`HydratedRouter` components for client-side routing, `createRequestHandler` for server-side request handling, and the `react-router` CLI for building and developing applications. Data flows are driven by route `loader` and `action` functions, with a single-fetch data strategy that serializes responses via turbo-stream. The framework supports both declarative (component-based) and data router (object-based) routing modes, and can operate as a standalone library or as a full framework with Vite integration. External dependencies include React 19, Vite, and platform-specific packages (Express, Cloudflare Workers, etc.). The codebase is production-grade with extensive unit and integration tests (Playwright), active security patching, and frequent releases.

This repository is the Remix framework monorepo, implemented as a modular collection of 50+ independently versioned TypeScript packages under `packages/*`, all re-exported through a single `remix` meta-package. In production it provides a full-stack web framework built directly on Fetch/Streams standards: a typed fetch-first router with composable middleware, a custom JSX/Virtual DOM component runtime with SSR, hydration, frames, and CSS-in-JS, an asset server and compiler pipeline, authentication/session/security middleware, typed data validation and relational data-table packages with migrations, and a CLI for scaffolding, development, testing, and database operations. The repository is not a single deployable application; demos such as bookstore, social-auth, timeboxer, i18n, SSE, and the docs sites are first-party consumers that exercise the framework end-to-end.

React Router's official documentation website (reactrouter.com). It is a React Router v8 framework application served by a custom Node HTTP server composed from @remix-run middleware libraries (fetch-router, node-fetch-server, static-files, compression, logger). The core function is serving versioned documentation: docs are not stored in this repo — they are fetched at runtime from the remix-run/react-router GitHub repository via raw content endpoints and tarballs, processed through a unified/remark/rehype markdown pipeline with Shiki syntax highlighting, and cached in LRU caches with 5-minute TTLs. Route loaders resolve URL segments to GitHub refs, fetch markdown, render it to HTML, and expose raw-markdown endpoints for clients that prefer them. URL structure encodes GitHub refs: /home serves the latest release tag, /main/* serves the main branch, /local/* reads from a locally-cloned react-router repo during development, and /7.15.1/* serves that exact semver tag. A React Router middleware chain enforces HTTPS, removes trailing slashes, redirects major-version shorthand URLs (/v7/* → latest 7.x), applies a Netlify-style _redirects file, and performs HTTP content negotiation so requests with an Accept preference for text/markdown (or a .md suffix) receive raw markdown instead of HTML, complete with a Vary: Accept header and an X-Markdown-Tokens size hint. The server layer adds a fixed-window rate limiter emitting standard RateLimit/Retry-After headers, proxy-aware client-IP resolution (Cloudflare, X-Forwarded-For, IPv4-mapped IPv6), static asset caching, and gzip/brotli compression tuned for streaming HTML. The app integrates Algolia DocSearch with version-faceted search, a color-scheme cookie action with optimistic UI, GitHub/npm statistics with graceful hard-coded fallbacks, SEO meta generation, and a full dark-mode Tailwind design system. CI/CD runs lint, typecheck, and Vitest coverage on every push, then deploys to Fly.io staging/production with Fastly cache purges. The repo is primarily an application, though its runtime behavior is a GitHub→markdown→HTML content pipeline for documentation. Craftsmanship is strong: the markdown toolchain (diff-aware code blocks, line numbers, a clever fake-hex Shiki theme trick to smuggle CSS custom properties through vscode-textmate), the content-negotiation logic, and the server middleware are all well-tested and mostly isolated into a modules/ directory explicitly intended for potential npm publication. Some warts exist — commented-out playground code, hard-coded stat fallbacks, and a couple of stale dependencies (shiki 0.14.7, lru-cache 7) — but none undermine the architecture.