Atlas · seriesPicking the libraries a React app leans on — the 2026 landscape, the tradeoffs, and a recommendation.
Use react-resizable-panels for fixed side-by-side splits and Dockview for VS Code-style rearrangeable docking — the tradeoffs, plus how to persist layouts and host grids/forms inside panes.
Five angles on picking a React i18n library in 2026 — the six-library head-to-head, message format, type safety, runtime fit, and the translation pipeline — converge on react-i18next as the safe default and the compile-time cohort (Paraglide, Lingui, next-intl) as where the momentum is.
Across five angles the answer converges: TanStack Router for a URL-as-state admin console, React Router as the safe default — and keep data-fetching out of the router either way.
Four candidates turned out to be three, then two: shadcn/ui now ships Base UI by default, so the real question is whether a Tailwind-4 monorepo should own its component code or vendor a library that must be talked out of overriding its own utilities.
Ship the SPA, not the BFF — but build it so the BFF is a 2–5 day retrofit, because the IETF names business apps explicitly and the supply-chain argument is the one that survives scrutiny.
openapi-typescript + openapi-fetch + openapi-react-query wins on every axis that matters for a .NET 10 ProblemDetails backend; Hey API is the runner-up; Orval fights TanStack's direction and Kiota's TypeScript is still in preview.
Sonner won the ecosystem on distribution, not merit — it is the right default, but it is polite-only, its repo is the quietest of the group, and no library solves the server boundary for you.
The field narrowed to three live options, and every angle lands on the same axis: what the grid owns versus what you write yourself — with the paywall sitting exactly on that line.
Seven angles on the 2026 React form stack: React Hook Form still wins, React's own primitives are a submission layer and not a form layer, Standard Schema made the validator swappable, and every hard pattern reduces to one question — where do the field values live.
Six angles independently converge: don't introduce Redux — generate the client from Forge's OpenAPI, let TanStack Query own server state, let the router own filter state, and leave one small Zustand store for what remains.