Empty gqlErrors in the useGqlError

[adamfir]

Environment

---

• Operating System: Darwin
• Node Version: v22.14.0
• Nuxt Version: 3.17.2
• CLI Version: 3.25.0
• Nitro Version: 2.11.11
• Package Manager: pnpm@9.15.2
• Builder: -
• User Config: compatibilityDate, devtools, modules, app, shadcn, runtimeConfig, graphql-client
• Runtime Modules: @nuxtjs/tailwindcss@6.14.0, @nuxt/icon@1.12.0, shadcn-nuxt@0.10.4, @pinia/nuxt@0.5.5, nuxt-graphql-client@0.2.46, @nuxt/image@1.10.0, pinia-plugin-persistedstate@4.2.0
• Build Modules: -

---

Describe the bug

Bug Report: err.gqlErrors is empty despite server response containing errors

Description

I'm encountering an issue where the err.gqlErrors array is always empty, even though the server's response includes a properly formatted errors array.

Steps to Reproduce

1. Make a GraphQL request that triggers an error.
2. Observe the response from the server. Example response:

   {
       "errors": [
           {
               "message": "login-error: Please retry after several minute",
               "locations": [
                   {
                       "line": 3,
                       "column": 3
                   }
               ],
               "path": [
                   "token"
               ],
               "extensions": {
                   "code": "INTERNAL_SERVER_ERROR",
                   "stacktrace": [
                       "Error: login-error: Please retry after several minute",
                       "    at AuthService.login (/path/to/auth.service.ts:76:13)",
                       "    at processTicksAndRejections (node:internal/process/task_queues:105:5)"
                   ]
               }
           }
       ],
       "metadata": {
           "request_id": "763229af-ff11-4fc6-bbba-bdb0ff77b2b0"
       }
   }

3. Handle errors using the useGqlError composable, and log err.gqlErrors. The array is empty.

Expected Behavior

The err.gqlErrors array should contain the errors field from the server response.

Actual Behavior

The err.gqlErrors array is empty.

Investigation

I have followed the recommendations provided in the documentation and ensured that:

• The server response includes a valid errors field.
• The client-side error handler is configured correctly.
• Network and parsing issues have been ruled out.

I suspect this issue might be related to how graphql-request (the parent library) processes or parses errors. It seems that the error response is not being properly passed to nuxt-graphql-client.

Is there any additional configuration or workaround I can implement to fix this issue? If the issue is indeed related to graphql-request, could you guide me on how to proceed?

Thank you for your help!

Expected behaviour

I expect the gqlErrors array is not empty

Reproduction

No response

Additional context

Below is the error handling configuration used:

export default defineNuxtPlugin(() => {
  useGqlError((err) => {
    console.error('GraphQL Error:', err);
    console.error('GqlErrors:', err.gqlErrors); // This is empty
  });
});

Logs

[adamfir]

Hi @Diizzayy ,

After further investigation, I’ve confirmed this is a regression that started in v0.2.38. In v0.2.36, the useGqlError composable returns the expected array of GraphQL errors, but in v0.2.38 and newer, gqlErrors is always empty—even though the server’s response contains errors.

This appears to be related to the dependency updates (such as graphql-request, Nuxt, or related internals) that landed in v0.2.38. It’s possible the error extraction logic or the error object structure changed between these versions.

Suggestions for investigation:

• Compare how errors are extracted/passed through from graphql-request in v0.2.36 vs v0.2.38.
• Check if error details are now available under a different property on the error object (e.g., err.response?.errors or err.rawError).
• As a workaround, users might temporarily extract errors from those other properties.

Let me know if you need any logs or a minimal reproduction. Thanks for your help!

[Diizzayy]

@adamfir Apologies for the delay here, I've been too busy for my own good. I'll spend sometime today looking into this

[adamfir]

@adamfir Apologies for the delay here, I've been too busy for my own good. I'll spend sometime today looking into this

No worries, in case anyone need some quick fix: since i suspect the problem is in the graphql-request, I've been trying to temporarily overrides the graphql-request version to 6.1.0. The gqlErrors now working as expected.

  "pnpm": {
    "overrides": {
      "graphql-request": "6.1.0"
    }
  }