Apollo Client Devtools
Extension Actions
CRX ID
jdkknkkbebbapilgoeccciglkfbmbnfm
Description from extension meta
GraphQL debugging tools for Apollo Client.
Image from store
Description from store
Apollo Client Devtools is a Chrome extension for the open-source GraphQL client, Apollo Client. This extension has 4 main features:
1. A built-in version of the Apollo Studio Explorer that allows you to make queries against your GraphQL server using your app's network interface directly (no configuration necessary).
2. A query watcher that shows you which queries are being watched by the current page, when those queries are loading, and what variables those queries are using.
3. A mutation inspector that displays the mutations made to your Apollo Client application data.
4. A cache inspector that displays your Apollo Client cache data. You can explore the cache through a tree-like interface, and search for specific field keys and values.
Code for this extension can be found at: https://github.com/apollographql/apollo-client-devtools
Any bugs can be reported by opening a new issue at: https://github.com/apollographql/apollo-client-devtools/issues/new
To learn more about Apollo, see: https://www.apollographql.com
Latest reviews
- Chloe Silent
- Don't work on chrome. Uselles extension
- Arno Hilke
- Invaluable for debugging
- Abhishek Ghosh
- Does not work on my chrome
- Aurora Apps
- Perfect
- Andrew Bonifacio
- Works like a charm
- Jacob Sebastian
- It works fine... Saver
- Steven Coltman
- Works :)
- Andrii Dovhopolov
- Extension does not work for Apollo Client 3.9.2 . It simply does not see GraphQL. window.__APOLLO_CLIENT__ is present. It's not a bug with GraphQL. connectToDevTools was EXPLICITLY set to true. App is running in dev mod. window.__APOLLO_DEVTOOLS_GLOBAL_HOOK__.ApolloClient IS present. Yes, my client is created within 10 sec of first load. No, waiting for another 10 sec did not help. "An Apollo Client instance was not found, either because an Apollo Client instance was never created, or because it could not be discovered. This is most commonly fixed by setting the connectToDevTools option to true."
- j l
- DOES NOT WORK ANYMORE. Uncaught runtime errors: ERROR Cannot convert object to primitive value TypeError: Cannot convert object to primitive value I thought it was something wrong with my app. No, its wrong with this plugin.
- Jakob Kielland
- Straight up doesn't show up in the UI. No sign of it even being installed, other than seeing in my list of extensions.
- Ivan Grekov
- My mf proj structure stoped working due to this ext, when I tried to switch between pages
- Kevin Marlow
- Wasted an entire day trying to figure out why my NextJS 13 app was failing in-app redirects. This was the culprit. Once I removed this, it all worked. The error I hit was "TypeError: Cannot convert object to primitive value" when loading some of my pages.
- M T
- nice
- mcquiggd
- Installed in edge, refreshed the page... and can now see queries, execute them in a useful dev environment. Useful.
- YoungJae Ji
- very sad. it's not working. I hope one day it will work but this is third time coming back realizing not gonna happen
- Brandon Moore
- Obnoxiously unnecessary. None of the projects I work on would be needed by this extension... but there's no way to prevent it from showing in the console log. (even if I add a filter, it will still display as a message). Why would the chrome developers force a message that isn't critical to the browser? I guess I'll have to start debugging the console in a different browser now.
- Grant Walker
- Mixed response. Sometimes the queries/cache populate, sometimes not. Currently its not working at all
- Mayank Mishra
- Doesn't work at all. Please fix this and update your extension after testing in every browser.
- Pouria Mirebrahimi
- It'a not working on chrome version 120 even
- Ralph Schmieder
- works perfectly fine with Chrome version 120. As others have noted, support must be enabled in your app.
- SᴇᴘSᴏʟ
- Does not work in the latest Chromium-based MS Edge
- Daniel Tendero
- Not working at all. With connectToDevTools to true neither
- Sebastian Findling
- It works fine after setting connectToDevTools to true in ApolloProvider.js (Oct 2023)
- Sebastian Findling
- It works fine after setting connectToDevTools to true in ApolloProvider.js (Oct 2023)
- Ярослав Ахромеев
- It's working but we have to be able to set the column's width, otherwise it's really hard to use the extension
- Ярослав Ахромеев
- It's working but we have to be able to set the column's width, otherwise it's really hard to use the extension
- Botond Bertalan
- Sorry, it does not work, even if I set: connectToDevTools to true. Also when I add it I get 3 build errors: 2 of them are: "Unhandled Runtime Error TypeError: Cannot read properties of undefined (reading 'getObservableQueries')" And the third is: "Unhandled Runtime Error Error: There was an error while hydrating. Because the error happened outside of a Suspense boundary, the entire root will switch to client rendering." It is on apple silicon and node v16
- Botond Bertalan
- Sorry, it does not work, even if I set: connectToDevTools to true. Also when I add it I get 3 build errors: 2 of them are: "Unhandled Runtime Error TypeError: Cannot read properties of undefined (reading 'getObservableQueries')" And the third is: "Unhandled Runtime Error Error: There was an error while hydrating. Because the error happened outside of a Suspense boundary, the entire root will switch to client rendering." It is on apple silicon and node v16
- Anonymous
- Update: it does work, but you have to explicitly set `connectToDevTools: true`, despite the documentation saying this is unnecessary in dev mode. https://www.apollographql.com/docs/react/development-testing/developer-tooling/#configuration
- Gio Romanadze
- not working
- Gio Romanadze
- not working
- Anatoliy Stukota
- The advice in the Chrome console is still bothering me, even with the installed Apollo DevTools
- Anatoliy Stukota
- The advice in the Chrome console is still bothering me, even with the installed Apollo DevTools
- Ben Chen
- Was not working for me until I explicitly set `connectToDevTools` to `true` https://www.apollographql.com/docs/react/development-testing/developer-tooling/#configuration Now it's working great in development.
- Ben Chen
- Was not working for me until I explicitly set `connectToDevTools` to `true` https://www.apollographql.com/docs/react/development-testing/developer-tooling/#configuration Now it's working great in development.
- Mathieu Lessard
- It works. It doesn't work. It works. It doesn't work. It works. It doesn't work. It is a very good tool. If it was dependable too it would be great.
- Mathieu Lessard
- It works. It doesn't work. It works. It doesn't work. It works. It doesn't work. It is a very good tool. If it was dependable too it would be great.
- Denis Senokosov (dennni)
- It just does not work
- Denis Senokosov (dennni)
- It just does not work
- Anonymous
- Works after installing and then removing and re-installing.
- Dominic Bouchard
- Doesn't work. No documentation whatsoever. No support/update. What is this?
- Dominic Bouchard
- Doesn't work. No documentation whatsoever. No support/update. What is this?
- Katleho Komeke
- I downloaded the chrome extension. It's not working. I also downloaded the firefox extension. Also not working. The extension doesn't even show up when you open the dev tools.
- Katleho Komeke
- I downloaded the chrome extension. It's not working. I also downloaded the firefox extension. Also not working. The extension doesn't even show up when you open the dev tools.
- Anonymous
- Doesn't work and isn't sufficiently documented
- Jason Perrone
- It doesn't do anything. The Queries tab, Mutations tab and Cache tab are all always blank, 100% of the time.
- Jason Perrone
- It doesn't do anything. The Queries tab, Mutations tab and Cache tab are all always blank, 100% of the time.
- Furnibay Shop
- Doesnt work on Mac OSX
- Furnibay Shop
- Doesnt work on Mac OSX
- Souvik Basu
- Most reviews mention that the extension is not working probably because they are trying to access a live site. It works perfectly well for http://localhost. If not try adding `connectToDevTools: true` property to your ApolloClient instance. The team should have mentioned this properly in the description