@tanstack/react-query
Hooks for managing, caching and syncing asynchronous and remote data in React
About
Hooks for managing, caching and syncing asynchronous and remote data in React
What detecting @tanstack/react-query tells you about a site
@tanstack/react-query reveals a clean separation between server state and UI state — the app caches, deduplicates and revalidates API data through React Query rather than stuffing it into Redux. Its presence is a strong marker of a modern, data-fetching-heavy React app built by a team that knows the current best practices.
Why the exact @tanstack/react-query version matters
The library was renamed from react-query to @tanstack/react-query at v4, and v5 changed the hook signatures (the single-object form) and dropped legacy overloads. The exact version tells you which API era the code uses and whether it has completed the v5 migration.
@tanstack/react-query in a real-world stack
When you find @tanstack/react-query in a bundle, it rarely travels alone. A fetch layer (axios, ky, or native fetch), and often zustand for the remaining UI state.
Quick facts
npm install @tanstack/react-queryCommon pairings
Packages this one expects to find in the same project. Each is also a Sourcemap Explorer detection target.
What @tanstack/react-query pulls in
@tanstack/react-query declares 1 direct dependency — each one also rides into any bundle that ships @tanstack/react-query, so they are detection targets too. Reading them is a quick way to understand the package's real footprint .
How Sourcemap Explorer detects @tanstack/react-query
@tanstack/react-query ships as v5.101.4, published 2026-07-21 and carries 1 direct dependency, 1 peer dependency (react), 523 versions on the registry. Those exact numbers are the footprint Sourcemap Explorer matches when @tanstack/react-query rides inside a deployed bundle — here is how the detection works.
We catch @tanstack/react-query from two complementary signals: bundled source paths and the embedded package.json. Modern bundlers (webpack, Vite, esbuild, Rollup, Turbopack) preserve the original node_modules/@tanstack/react-query/ paths inside the JavaScript sourcemap's sources[] array — that's the canonical signal. When the matching package.json is also captured in sourcesContent[], we read the exact version field — patch number included. No regex guessing, no version inference.
- 1
Confirm the site exposes sourcemaps
In DevTools Network, check the response headers of any application script for `SourceMap` or `X-SourceMap`. Failing that, fetch the script's last 4 KB and look for a `//# sourceMappingURL=` comment — that map is where the `@tanstack/react-query` paths live.
- 2
Find the package in the bundle
Open DevTools → Network → reload. Click any application script and look at its sourcemap. Inside, search `sources[]` for entries matching `node_modules/@tanstack/react-query/` — every match confirms the package is bundled. The matching `sourcesContent[i]` for `node_modules/@tanstack/react-query/package.json` gives you the exact installed version.
- 3
Read the version directly from package.json
Run `jq -r '. as $m | $m.sources | to_entries[] | select(.value | endswith("node_modules/@tanstack/react-query/package.json")) | $m.sourcesContent[.key] | fromjson | .version' bundle.js.map`. Sourcemap Explorer automates the same query in the popup.
Major releases of @tanstack/react-query
When each major version first landed. Major bumps are where breaking changes live, so this timeline is the fastest way to date the @tanstack/react-query version a site actually ships against the ecosystem.
Recent versions
@tanstack/react-query README
Live mirror of the GitHub README, for reference. Updated whenever the repo's default branch changes.
TanStack Query
An async state management library built to simplify fetching, caching, synchronizing, and updating server state.
- Protocol‑agnostic fetching (REST, GraphQL, promises, etc.)
- Caching, refetching, pagination & infinite scroll
- Mutations, dependent queries & background updates
- Prefetching, cancellation & React Suspense support
Read the docs →
Get Involved
- We welcome issues and pull requests!
- Participate in GitHub discussions
- Chat with the community on Discord
- See CONTRIBUTING.md for setup instructions
Partners
|
|
We're looking for TanStack Query Partners to join our mission! Partner with us to push the boundaries of TanStack Query and build amazing things together.
LET'S CHATExplore the TanStack Ecosystem
- TanStack Config – Tooling for JS/TS packages
- TanStack DB – Reactive sync client store
- TanStack DevTools – Unified devtools panel
- TanStack Form – Type‑safe form state
- TanStack Pacer – Debouncing, throttling, batching
- TanStack Query – Async state & caching
- TanStack Ranger – Range & slider primitives
- TanStack Router – Type‑safe routing, caching & URL state
- TanStack Start – Full‑stack SSR & streaming
- TanStack Store – Reactive data store
- TanStack Table – Headless datagrids
- TanStack Virtual – Virtualized rendering
… and more at TanStack.com »
FAQ
What is @tanstack/react-query used for?
Hooks for managing, caching and syncing asynchronous and remote data in React
How can I tell if a website is using @tanstack/react-query?
Open the page in Chrome with the Sourcemap Explorer extension installed and read the Stack tab. We catch `@tanstack/react-query` from two complementary signals: `node_modules/@tanstack/react-query/` paths inside the JavaScript sourcemap, and the embedded `package.json` we read for exact-version detection. Without the extension you can do the same lookup manually in DevTools — the steps are listed in the "How Sourcemap Explorer detects" section above.
How do I find out which version of @tanstack/react-query a website is running?
Read it straight from the site's JavaScript sourcemap. When a build ships source maps, the bundled `@tanstack/react-query/package.json` carries the exact `version` string — Sourcemap Explorer extracts it in one click on the Stack tab, and you can do it by hand in DevTools by opening the `.map` file and searching for `node_modules/@tanstack/react-query/package.json`. That is far more reliable than inferring the version from an asset-hash or a `?ver=` query string, which is all surface-level detectors have to go on. The current npm release is 5.101.4, but real deployments frequently run an older pinned version — which is exactly why reading the bundled number matters.
What is the latest version of @tanstack/react-query?
5.101.4, as published on the npm registry. The "Recent versions" table on this page lists the most recent 8 releases with their release dates. Sourcemap Explorer reports the version actually bundled into a site, which can lag the latest release by months on real-world deployments.
Is @tanstack/react-query actively maintained?
Very actively maintained — the last release shipped within the past three months. The last published release was 2026-07-21. Source code: https://github.com/TanStack/query.
Where can I read more?
Project homepage: https://tanstack.com/query. Source code: https://github.com/TanStack/query. Published on npm: https://www.npmjs.com/package/@tanstack/react-query. Licensed as MIT.
Detected by Sourcemap Explorer
When a bundle ships sourcemaps, we read the embedded package.json for @tanstack/react-query and report the precise version (the registry's latest is v5.101.4, published 2026-07-21; the bundled copy is often older). Without sourcemaps, an import / require in the page's scripts is enough to flag it.