A new panel, built for GraphQL

A new tab in Chrome DevTools that shows the information you need. Using the interface you already know.

Why

All your requests go to the same endpoint

All you could see was a list of POST /graphql with status 200. GraphQL Network shows you what you actually care about.

Chrome Network
NameStatusType
graphql200fetch
graphql200fetch
graphql200fetch
graphql200fetch
graphql200fetch

The error in the third request only shows up if you open its response.

GraphQL Network
NameStatusType
Godsokquery
CreateGodokmutation
GetUser1 errorquery
GetEventsokquery
GodActionoksubscription

Operation name, type and errors at a glance.

Payload

Query, variables and files in a single view

The Payload tab separates the operation from its variables and attached files, with GraphQL highlighting.

Query
1  mutation UploadFavicon($file: File!) {
2    uploadFavicon(file: $file) {
3      name
4      size
5      __typename
6    }
7  }
Variables View source
file: null
Files
1favicon.ico· image/x-icon
Timing

Analyze every millisecond

The breakdown separates each phase of the request. If waiting dominates, the problem is in the resolver.

CreateGodmutation · 184.6 ms
Queued1.2 ms
Initial connection6.8 ms
SSL12.4 ms
Request sent0.6 ms
Waiting for server148.2 ms
Content download15.4 ms
Real time

Subscriptions over WebSocket and SSE

Every message sent and received appears in order, with its time and size. The connection stays open for as long as the subscription is active.

GodAction · subscription · wsOpen
Sent{"type":"connection_init","payload":{}}12:04:01
Received{"type":"connection_ack"}12:04:01
Sent{"id":"1","type":"subscribe","payload":{"query":"subscription GodAction…"}}12:04:01
Received{"id":"1","type":"next","payload":{"data":{"godAction":{"god":"Hermes"}}}}12:04:09
Received{"id":"1","type":"next","payload":{"data":{"godAction":{"god":"Athena"}}}}12:04:15
Received{"id":"1","type":"next","payload":{"data":{"godAction":{"god":"Zeus"}}}}12:04:22
Interface

No new tools to learn

The interface mirrors Chrome DevTools: filters, waterfall, detail panel and tabs in the same place. Open DevTools and start debugging.

Available on the Chrome Web Store

Cut the friction of working with GraphQL and start using tools that make your job easier.

Go to Chrome Web Store