Frontend45-60 min
React Query Server State Setup
Create a QueryClient, write reusable query hooks, use mutations, and keep server state out of ad hoc component state.
ReactTanStack QueryREST
Prerequisites
- A React app that fetches data from an API.
- At least one list endpoint and one mutation endpoint.
- A consistent API client function.
1
Plan the implementation
Start by choosing the exact page, route, API, or deployment surface you want to improve. A narrow target makes the implementation measurable and easier to verify.
- Write down the current behavior and the user-facing problem it creates.
- Pick one measurable success signal such as bundle size, latency, error rate, security coverage, or UI responsiveness.
- Identify the files, routes, providers, and environment variables involved.
- Create a rollback note before changing production-sensitive configuration.
2
Set up the required tools
Install or configure only the tools needed for this implementation. Keep config close to the feature so future developers can find the moving parts quickly.
Implementation snippet
npm install @tanstack/react-queryChecklist
- Dependencies are added to the correct workspace package.
- Environment variables are documented in `.env.example` when needed.
- Local development still starts without production-only secrets.
- The change is small enough to review in one pull request.
3
Implement the core pattern
- Wrap the app in `QueryClientProvider` once.
- Move fetch calls into query hooks with stable query keys.
- Set retry behavior based on the endpoint type.
- Use mutations for create, update, and delete actions.
- Invalidate or update affected query data after successful mutations.
Implementation snippet
const queryClient = new QueryClient();
<QueryClientProvider client={queryClient}>
<App />
</QueryClientProvider>
export function useProjects() {
return useQuery({ queryKey: ["projects"], queryFn: api.getProjects });
}4
Handle edge cases
Checklist
- Loading and error states are handled per screen.
- Query keys include filters, page numbers, and user scope.
- Mutations do not leave stale UI behind.
- Sensitive data is not persisted to unsafe storage.
5
Verify before production
- Run the app locally and test the normal success path.
- Test one failure path, one empty state, and one slow-network or retry path.
- Run the project build and any related unit or integration tests.
- Check browser console, server logs, and network responses for hidden warnings.
- Document the final behavior, commands used, and any follow-up work.