chore(deps): update dependency graphql-request to v7.4.0

[renovate]

This PR contains the following updates:

Package	Change	Age	Confidence
graphql-request (source)	7.3.1 → 7.4.0

---

Release Notes

graffle-js/graffle (graphql-request)

v7.4.0

Compare Source

What's Changed

Features

• Expose response headers and body on error responses - Added headers and body properties to GraphQLResponse and GraphQLClientResponse types, making it easier to access non-GraphQL response data (e.g., 401/403/503 errors that return plain JSON instead of GraphQL).

Contributors

• @​adambrgmn (#​1476)

Full Changelog: graffle-js/graffle@7.3.5...7.4.0

v7.3.5

Compare Source

What's Changed

• feat: support TypedDocumentString from graphql-codegen by @​jasonkuhrt in #​1456
• fix: parse GraphQL errors from response body on HTTP 4xx/5xx status codes by @​jasonkuhrt in #​1457
• Fix: handle non-JSON error responses gracefully by @​jasonkuhrt in #​1459
• Revert PRs #​1457 and #​1459 - will reimplement properly by @​jasonkuhrt in #​1463
• Fix: parse GraphQL errors from 4xx/5xx responses (#​1281) by @​jasonkuhrt in #​1465
• fix: add TypedDocumentString to accepted document types by @​jasonkuhrt in #​1468

Full Changelog: graffle-js/graffle@v7.3.0...v7.3.5

v7.3.4

Compare Source

Bug Fixes

• Fixed #​1281: GraphQL errors and data are now accessible from 4xx/5xx HTTP responses
• Fixed #​1461: ClientError is properly returned for non-2xx responses with malformed bodies
• Fixed #​1462: ClientError is properly returned for non-2xx responses with unsupported content types

Changes

• Non-2xx HTTP responses now parse the response body first to extract GraphQL errors/data when available
• Non-2xx responses with valid GraphQL bodies return ClientError with errors and data accessible
• Non-2xx responses with invalid bodies still return ClientError (not generic Error) for backwards compatibility
• This release reverts PRs #​1457 and #​1459 which introduced regressions, then reapplies a minimal fix for #​1281

Breaking Changes

None - this release maintains backwards compatibility while adding support for accessing GraphQL errors from 4xx/5xx responses.

v7.3.3

Compare Source

Bug Fixes

• Non-JSON Error Response Handling: Fixed regression in 7.3.2 where servers returning HTTP 4xx/5xx status codes with non-JSON response bodies (HTML, plain text) would throw an unhelpful error: "Invalid execution result: result is not object or array" (#​1459, closes #​1458)
  • Added safe JSON parsing fallback for responses without proper Content-Type headers
  • Returns descriptive error messages with response body preview for non-JSON responses
  • Handles common production scenarios: load balancer errors (502/503 HTML pages), CDN errors, WAF/firewall responses, misconfigured servers
  • Maintains backward compatibility for servers that omit Content-Type but return valid JSON
  • Added comprehensive test coverage for HTML, plain text, and missing Content-Type scenarios

What Changed

Version 7.3.2 introduced a bug where the ELSE branch in parseResultFromResponse would pass raw strings (HTML, plain text) to a parser expecting objects/arrays. This only surfaced when:

1. Server returns 4xx/5xx status code
2. Content-Type header is missing or non-JSON (e.g., text/html, text/plain)
3. Response body is not valid JSON

This is now fixed with graceful error handling and clear error messages.

v7.3.2

Compare Source

Bug Fixes

• HTTP Error Handling: Fixed regression from v6 to v7 where HTTP 4xx/5xx responses would not include GraphQL errors from response body in ClientError (#​1457, closes #​1281)

  • Response body is now parsed before checking HTTP status
  • Users can access GraphQL errors via error.response.errors even with non-2xx status codes
  • Common use case: authentication errors (422), server errors (500)

• graphql-codegen Compatibility: Added support for TypedDocumentString from @graphql-codegen when using documentMode: 'string' (#​1456, closes #​1453)

  • Handles boxed String objects created by TypedDocumentString class
  • Normalizes document input to prevent crashes when passing to GraphQL operations

---

Configuration

📅 Schedule: (UTC)

• Branch creation
  • At any time (no schedule defined)
• Automerge
  • At any time (no schedule defined)

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• If you want to rebase/retry this PR, check this box

---

This PR was generated by Mend Renovate. View the repository job log.

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 18.75%. Comparing base (0631803) to head (87d65c8).

Additional details and impacted files

@@           Coverage Diff           @@
##           master     #142   +/-   ##
=======================================
  Coverage   18.75%   18.75%           
=======================================
  Files          10       10           
  Lines         192      192           
  Branches       41       41           
=======================================
  Hits           36       36           
  Misses        156      156           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.