GraphQL Network Inspector
开发者工具 / Developer Tools
Simple and clean network inspector for GraphQL
用户数
100K
评分
4.6
评论数
138
7 天增长
0|0%
稳定信号未识别到付费功能中风险权限组合
Apollo Client Devtools
GraphQL debugging tools for Apollo Client.
用户数200K当前公开安装规模
评分2.7商店平均评分
评论数269公开评论体量
Manifest 版本V3插件平台版本
7日增长0近 7 天净增用户
7日增长率0%相对周增长速度
视觉预览
1 项素材Apollo Client Devtools 媒体预览
趋势
用户增长趋势
按已采集快照查看用户数变化。
用户增长趋势
评分趋势
近 7 日评分趋势
展示最近 7 日窗口内已采集的评分快照，辅助判断近期评分是否稳定。
7 日评分变化
起始值
2.71
最新值
2.71
7 日评分变化
0.00
2026年7月13日2026年7月19日
增长概览
日/周/月增长表现
同口径展示 1 天、7 天、30 天的绝对增长与增长率。
1日增长持平
00%7日增长持平
00%30日增长持平
00%技术摘要
版本、语言与抓取信息
查看发布时间、版本、支持语言、最近更新和抓取时间。
版本4.25.0
ManifestV3
大小551KiB
语言数1English (United States)
发布时间
最近更新
最近抓取
English (United States)
简介
插件简介
查看插件说明、主要功能和适用场景。
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
评价
最新评论快照
查看最近评论和评分分布。
商店综合星级2.7Chrome 商店给出的聚合评分，包含只有打分但没有同步评论正文的情况
已同步评论均分2.3仅基于下方已同步评论正文计算
有内容评论198已同步的评论正文数量
总评分/评论数269Chrome 商店公开评分/评论计数
商店综合星级：2.7。下方星级分布只统计已同步评论正文；如果某个插件只有公开分数、没有真实评论正文，这里可能为空。
相关推荐
同类与相关插件
查看 Chrome 商店详情页中的相关产品。
React Developer Tools
开发者工具 / Developer Tools
Adds React debugging tools to the Chrome Developer Tools. Created from revision 3cde211b0c on 10/20/2025.
用户数
5M
评分
4.0
评论数
1,634
7 天增长
0|0%
GraphQL DevTools
开发者工具 / Developer Tools
Build an extremely useful tool to manage graphQL queries !
用户数
3K
评分
3.5
评论数
8
7 天增长
0|0%
Altair GraphQL Client
开发者工具 / Developer Tools
免费增值置信度 64
A beautiful feature-rich GraphQL Client for all platforms.
用户数
50K
评分
4.5
评论数
68
7 天增长
0|0%
Vue.js devtools
开发者工具 / Developer Tools
DevTools browser extension for Vue.js
用户数
1M
评分
4.1
评论数
2,171
7 天增长
0|0%
React Context DevTool
开发者工具 / Developer Tools
Devtool for React Context and useReducer
用户数
30K
评分
4.2
评论数
26
7 天增长
-10K|-25%
Works :)
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."
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.
Straight up doesn't show up in the UI. No sign of it even being installed, other than seeing in my list of extensions.
My mf proj structure stoped working due to this ext, when I tried to switch between pages
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.
nice
Installed in edge, refreshed the page... and can now see queries, execute them in a useful dev environment. Useful.
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.
Mixed response. Sometimes the queries/cache populate, sometimes not. Currently its not working at all