React Query SPA

React + TanStack Query for server-state SPAs.

FrontendModerate

Stack Components

FrameworkReact 19

DataTanStack Query 5

BuildVite 6

StylingTailwindCSS 4

Why

Declarative data fetching, caching, and optimistic updates. JavaScript is used by 62% of developers per the Stack Overflow 2024 survey, and React holds 40% framework market share (State of JS 2024).

Vite replaced Webpack as the default bundler, cutting dev server startup from 30s to <1s.

When

Use for data-heavy dashboards. Avoid for local-only state apps.

How

1. npm create vite@latest -- --template react-ts 2. npm i @tanstack/react-query 3. Wrap app in QueryClientProvider 4. Use useQuery hooks

Example

const { data } = useQuery({ queryKey: ['todos'], queryFn: fetchTodos }) return <ul>{data?.map(t => <li key={t.id}>{t.title}</li>)}</ul>

Common Problems

⚠Stale cache bugs — set staleTime and gcTime correctly
⚠Query key collisions — use hierarchical keys
⚠Configuration drift between environments — use infrastructure-as-code (Terraform/Pulumi) to keep dev/staging/prod identical

Best Practices

✓Use queryClient.setQueryData for optimistic updates
✓Enable devtools in development
✓Set up health checks and graceful shutdown — handle SIGTERM to drain in-flight requests before exit

FAQ

What is React Query SPA and what projects is it for?

React + TanStack Query for server-state SPAs. It pairs layered technologies for end-to-end type safety and out-of-the-box deploys, fitting everything from MVPs to production SaaS.

How do I spin up a working demo with React Query SPA in 10 minutes?

Two steps: (1) npm create vite@latest -- --template react-ts; (2) npm i @tanstack/react-query. Get the local dev server running, then wire one real data source to verify the end-to-end loop.

What is the most common pitfall with React Query SPA and how do I avoid it?

The most common pitfall is: Stale cache bugs — set staleTime and gcTime correctly. Avoid it by adding the matching checklist to your PR template and running type-check + lint + unit tests in CI — three gates before merge.

What are the best practices for React Query SPA?

Best practices for React Query SPA include: Use queryClient.setQueryData for optimistic updates; Enable devtools in development; Set up health checks and graceful shutdown — handle SIGTERM to drain in-flight requests before exit. The first one — "Use queryClient.setQueryData for optimistic updates" — should be set up at project init to avoid costly rework later.

When should I NOT choose React Query SPA?

Pick something else in three cases: (1) the team has zero experience with the core framework and the deadline is tight (learning-curve risk); (2) it's a pure content/marketing site (Astro is lighter); (3) you need very high throughput (>10k RPS) or strict-consistency microservices (Go/Rust). React Query SPA shines for mid-to-high complexity full-stack and API work — don't over-engineer simple static pages with it.