@apollo/client
A fully-featured caching GraphQL client.
About
A fully-featured caching GraphQL client.
What detecting @apollo/client tells you about a site
@apollo/client reveals a GraphQL data layer with a normalised client-side cache — the app queries a GraphQL API and Apollo manages caching, optimistic updates and local state. Its presence is a strong signal of a GraphQL-first backend contract.
Why the exact @apollo/client version matters
Apollo Client's cache configuration and React hooks API evolved across v3's minor releases, and v4 is a larger shift. The exact version tells you which hook and cache API the code targets and how current the GraphQL tooling is.
@apollo/client in a real-world stack
When you find @apollo/client in a bundle, it rarely travels alone. graphql (always), and a framework like Next.js or a Vite SPA around it.
Quick facts
npm install @apollo/clientThis package powers Apollo
The @apollo/client package is the canonical implementation of Apollo. Sourcemap Explorer uses this exact npm package as the framework-level fingerprint when it flags Apollo on a page — both via the bundled node_modules/@apollo/client/ source paths and via the embedded package.json inside the JavaScript sourcemap.
Common pairings
Packages this one expects to find in the same project. Each is also a Sourcemap Explorer detection target.
What @apollo/client pulls in
@apollo/client declares 7 direct dependencies — each one also rides into any bundle that ships @apollo/client, so they are detection targets too. Reading them is a quick way to understand the package's real footprint .
How Sourcemap Explorer detects @apollo/client
@apollo/client ships as v4.3.2, published 2026-10-05 and carries 7 direct dependencies, 6 peer dependencies (rxjs, react, graphql), 728 versions on the registry. Those exact numbers are the footprint Sourcemap Explorer matches when @apollo/client rides inside a deployed bundle — here is how the detection works.
We catch @apollo/client from two complementary signals: bundled source paths and the embedded package.json. Modern bundlers (webpack, Vite, esbuild, Rollup, Turbopack) preserve the original node_modules/@apollo/client/ 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 `@apollo/client` 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/@apollo/client/` — every match confirms the package is bundled. The matching `sourcesContent[i]` for `node_modules/@apollo/client/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/@apollo/client/package.json")) | $m.sourcesContent[.key] | fromjson | .version' bundle.js.map`. Sourcemap Explorer automates the same query in the popup.
Major releases of @apollo/client
When each major version first landed. Major bumps are where breaking changes live, so this timeline is the fastest way to date the @apollo/client version a site actually ships against the ecosystem.
Recent versions
@apollo/client README
Live mirror of the GitHub README, for reference. Updated whenever the repo's default branch changes.
Apollo Client
The industry-leading GraphQL client for TypeScript, JavaScript, React, Vue, Angular, and more. Apollo Client delivers powerful caching, intuitive APIs, and comprehensive developer tools to accelerate your app development.
➡️ Get Started with Apollo Client →
❓ Why Choose Apollo Client?
✅ Zero-config caching - Intelligent caching out of the box
✅ Framework agnostic - Works with React, Vue, Angular, Svelte, and vanilla JavaScript
✅ TypeScript-first - Full type safety and IntelliSense support
✅ React 19 ready - Supports Suspense, RSC, Compiler, and more
✅ Production-tested - Powers countless apps worldwide that serve millions of end users
🚀 Quick Start
npm install @apollo/client graphql
Apollo Client Skill
Give your AI agent specialized Apollo Client knowledge and setup guidance:
npx skills add apollographql/skills --skill apollo-client
💡 Resources
| Resource | Description | Link |
|---|---|---|
| Getting Started Guide | Complete setup and first query | Start Here → |
| Full Documentation | Comprehensive guides and examples | Read Docs → |
| API Reference | Complete API documentation | Browse API → |
| VS Code Extension | Enhanced development experience | Install Extension → |
| DevTools | Debug your GraphQL apps | Chrome | Firefox |
| Free Course | Learn GraphQL and Apollo Client | Take Course → |
💬 Get Support
Need help? We're here for you:
- Community Forum - Q&A and discussions
- GraphQL Discord - Real-time chat with the community
🧑🚀 About Apollo
Deliver tomorrow's roadmap today with our comprehensive suite of API orchestration tools:
- Apollo Client - Type-safe apps with GraphQL-powered on-device caching (React, iOS, Kotlin)
- Apollo Connectors - Compose all your GraphQL and REST APIs into one GraphQL endpoint
- Apollo MCP Server - AI needs APIs. The fastest way to ship reliable AI experiences
- Apollo Router - Scale your APIs seamlessly with GraphQL Federation, Security, Auth, and more
- GraphOS - Deploy, manage, govern, and explore your APIs (start for free, no credit card needed)
Explore the Complete Apollo Platform →
🛠️ Maintained by
| Name | Username |
|---|---|
| Jeff Auriemma | @bignimbus |
| Jerel Miller | @jerelmiller |
| Lenz Weber-Tronic | @phryneas |
Versioning Policy
While Apollo Client follows SemVer, it might introduce changes like changing transpilation targets, updating dependencies or dropping support for older versions of dependencies in minor releases. For more details, see our Versioning Policy.
🗺️ Roadmap
We regularly update our public roadmap with the status of our work-in-progress and upcoming features.
📣 Tell us what you think
| ☑️ Apollo Client User Survey |
|---|
| What do you like best about Apollo Client? What needs to be improved? Please tell us by taking a one-minute survey. Your responses will help us understand Apollo Client usage and allow us to serve you better. |
🗓️ Events
Join these live events to meet other GraphQL users and learn more:
🎪 Apollo Summit 2026
Oct 6-8, 2026 • San Francisco
1000+ engineers, talks, workshops, and office hours
🏆 Contributing
Thank you for your interest in submitting a Pull Request to Apollo Client! Read our guidelines first, and don't hesitate to get in touch.
New to open source? Check out our Good First Issues to get started.
🤝 Code of Conduct
Please read our Code of Conduct. This applies to any space run by Apollo, including our GitHub repositories, the Apollo GraphOS Discord, the Apollo GraphQL Forum. The Code of Conduct reflects our commitment to making the Apollo Community a welcoming and safe space in which individuals can interact.
🪪 License
Source code in this repository is available under the terms of the MIT License. Read the full text here.
FAQ
What is @apollo/client used for?
A fully-featured caching GraphQL client.
How can I tell if a website is using @apollo/client?
Open the page in Chrome with the Sourcemap Explorer extension installed and read the Stack tab. We catch `@apollo/client` from two complementary signals: `node_modules/@apollo/client/` 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 @apollo/client a website is running?
Read it straight from the site's JavaScript sourcemap. When a build ships source maps, the bundled `@apollo/client/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/@apollo/client/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 4.3.2, but real deployments frequently run an older pinned version — which is exactly why reading the bundled number matters.
What is the latest version of @apollo/client?
4.3.2, 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 @apollo/client actively maintained?
Very actively maintained — the last release shipped within the past three months. The last published release was 2026-10-05. Source code: https://github.com/apollographql/apollo-client.
What is the relationship between @apollo/client and Apollo?
@apollo/client is the canonical npm package for Apollo. Sourcemap Explorer treats finding `@apollo/client` in a bundle as the framework-level signal that Apollo is on the page, and the page you're reading is the canonical Sourcemap Explorer entry for the package itself.
Where can I read more?
Project homepage: https://www.apollographql.com/docs/react/. Source code: https://github.com/apollographql/apollo-client. Published on npm: https://www.npmjs.com/package/@apollo/client. Licensed as MIT.
Keep reading on Sourcemap Explorer
Detected by Sourcemap Explorer
When a bundle ships sourcemaps, we read the embedded package.json for @apollo/client and report the precise version (the registry's latest is v4.3.2, published 2026-10-05; the bundled copy is often older). Without sourcemaps, an import / require in the page's scripts is enough to flag it.