<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>DEV Community: Mr Bee</title>
    <description>The latest articles on DEV Community by Mr Bee (@melliforge).</description>
    <link>https://dev.to/melliforge</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F4196137%2F61787567-0f27-473a-a19f-1ac9a382cbdc.png</url>
      <title>DEV Community: Mr Bee</title>
      <link>https://dev.to/melliforge</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/melliforge"/>
    <language>en</language>
    <item>
      <title>How to debug GraphQL requests in Chrome DevTools</title>
      <dc:creator>Mr Bee</dc:creator>
      <pubDate>Sat, 21 Nov 2026 18:08:35 +0000</pubDate>
      <link>https://dev.to/melliforge/how-to-debug-graphql-requests-in-chrome-devtools-330p</link>
      <guid>https://dev.to/melliforge/how-to-debug-graphql-requests-in-chrome-devtools-330p</guid>
      <description>&lt;p&gt;Every GraphQL request looks the same in the Network tab: &lt;code&gt;POST /graphql&lt;/code&gt;, status 200, again and again. Here is how to find the one you care about with plain Chrome DevTools, where that stops working, and a free extension I built for the rest.&lt;/p&gt;

&lt;h2&gt;
  
  
  1. Filter the Network tab down to GraphQL
&lt;/h2&gt;

&lt;p&gt;Open DevTools (F12), go to &lt;strong&gt;Network&lt;/strong&gt;, and type &lt;code&gt;graphql&lt;/code&gt; in the filter box. To hide the preflight &lt;code&gt;OPTIONS&lt;/code&gt; requests too, filter with &lt;code&gt;method:POST graphql&lt;/code&gt;.&lt;/p&gt;

&lt;p&gt;Most clients send every operation to the same URL, so the list still shows one identical row per request. To tell them apart, click a row and open &lt;strong&gt;Payload&lt;/strong&gt;: the request body has &lt;code&gt;operationName&lt;/code&gt;, &lt;code&gt;query&lt;/code&gt; and &lt;code&gt;variables&lt;/code&gt;.&lt;/p&gt;

&lt;p&gt;Tip: click the &lt;strong&gt;Size&lt;/strong&gt; or &lt;strong&gt;Time&lt;/strong&gt; column header to sort by it and spot the heavy or slow operations quickly.&lt;/p&gt;

&lt;h2&gt;
  
  
  2. Don't trust the 200
&lt;/h2&gt;

&lt;p&gt;A GraphQL server usually answers with HTTP 200 even when the operation failed. The failure is in the body:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight json"&gt;&lt;code&gt;&lt;span class="p"&gt;{&lt;/span&gt;
  &lt;span class="nl"&gt;"data"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt; &lt;span class="nl"&gt;"user"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="kc"&gt;null&lt;/span&gt; &lt;span class="p"&gt;}&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;
  &lt;span class="nl"&gt;"errors"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="p"&gt;[&lt;/span&gt;&lt;span class="p"&gt;{&lt;/span&gt; &lt;span class="nl"&gt;"message"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="s2"&gt;"Not authorised"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="nl"&gt;"path"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="p"&gt;[&lt;/span&gt;&lt;span class="s2"&gt;"user"&lt;/span&gt;&lt;span class="p"&gt;]&lt;/span&gt; &lt;span class="p"&gt;}&lt;/span&gt;&lt;span class="p"&gt;]&lt;/span&gt;
&lt;span class="p"&gt;}&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;So check &lt;strong&gt;Preview&lt;/strong&gt; or &lt;strong&gt;Response&lt;/strong&gt; for an &lt;code&gt;errors&lt;/code&gt; array, not just the status column. &lt;code&gt;data&lt;/code&gt; can be partly filled in alongside errors, which is easy to miss.&lt;/p&gt;

&lt;h2&gt;
  
  
  3. Batched and persisted queries
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Batched requests&lt;/strong&gt; send an array of operations in one request. The &lt;strong&gt;Payload&lt;/strong&gt; shows an array, and the response is an array in the same order.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Persisted queries&lt;/strong&gt; (for example Apollo's automatic persisted queries) often send only a hash, in &lt;code&gt;extensions.persistedQuery.sha256Hash&lt;/code&gt;, and no query text. You'll only see the full query on the request that registers it, after a cache miss.&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  4. Subscriptions over WebSockets
&lt;/h2&gt;

&lt;p&gt;Subscriptions using &lt;code&gt;graphql-ws&lt;/code&gt; don't show up as normal requests. Filter the Network tab with &lt;strong&gt;Socket&lt;/strong&gt; (WS), select the connection and open &lt;strong&gt;Messages&lt;/strong&gt;: each &lt;code&gt;next&lt;/code&gt; message is one subscription event, with its &lt;code&gt;id&lt;/code&gt; matching the &lt;code&gt;subscribe&lt;/code&gt; message that started it.&lt;/p&gt;

&lt;h2&gt;
  
  
  5. Replay a request
&lt;/h2&gt;

&lt;p&gt;Right-click a request and choose &lt;strong&gt;Copy → Copy as cURL&lt;/strong&gt; or &lt;strong&gt;Copy as fetch&lt;/strong&gt; to run it again in a terminal or the console. Edit the &lt;code&gt;variables&lt;/code&gt; in the copied body to try other inputs.&lt;/p&gt;

&lt;h2&gt;
  
  
  Where this gets painful
&lt;/h2&gt;

&lt;p&gt;On a real app you end up opening request after request to read &lt;code&gt;operationName&lt;/code&gt;, scrolling through WebSocket frames to follow a subscription, and copying requests out to change one variable. There's also no easy way to see a failing or slow response in the UI without changing the server.&lt;/p&gt;

&lt;p&gt;That's why I built &lt;strong&gt;Wireglass&lt;/strong&gt;, a free Chrome extension (disclosure: I'm its author). It adds a GraphQL tab to DevTools that:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;lists each operation &lt;strong&gt;by name&lt;/strong&gt;, with batches split into their operations, persisted queries labelled, and subscriptions over WebSockets included;&lt;/li&gt;
&lt;li&gt;shows the errors in each response, not just the status;&lt;/li&gt;
&lt;li&gt;can show operations on a &lt;strong&gt;timeline&lt;/strong&gt;, to see what ran in parallel and which request likely waited on another's data;&lt;/li&gt;
&lt;li&gt;opens any operation in a full &lt;strong&gt;client&lt;/strong&gt; to edit and replay it, with schema autocomplete in the query and the variables;&lt;/li&gt;
&lt;li&gt;can &lt;strong&gt;mock&lt;/strong&gt; a response per site (replace, patch, delay or fail it) to test error and loading states without touching the server.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;It has no account, no analytics and no server: everything stays in your browser.&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Docs, with short videos: &lt;a href="https://wireglass.pages.dev/devtools/traffic/" rel="noopener noreferrer"&gt;https://wireglass.pages.dev/devtools/traffic/&lt;/a&gt;
&lt;/li&gt;
&lt;li&gt;Chrome Web Store: &lt;a href="https://chromewebstore.google.com/detail/wireglass/dmdokojnlojcmjbaghelooolbcabkfed?utm_source=devto" rel="noopener noreferrer"&gt;https://chromewebstore.google.com/detail/wireglass/dmdokojnlojcmjbaghelooolbcabkfed?utm_source=devto&lt;/a&gt;
&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;If you debug GraphQL another way, I'd like to hear how in the comments.&lt;/p&gt;

</description>
      <category>graphql</category>
      <category>webdev</category>
      <category>javascript</category>
      <category>tutorial</category>
    </item>
  </channel>
</rss>
