Update dependency graphql-request to ^7.4.0

[renovate]

This PR contains the following updates:

Package	Change	Age	Confidence
graphql-request (source)	^7.1.2 -> ^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

v7.3.1

Compare Source

Bug Fixes

• Fixed broken example links on npmjs.com (#​1332)
  • Updated package.json repository metadata to point to correct location: graffle-js/graffle
  • Updated homepage URL to include /tree/graphql-request path
  • Updated bugs URL to point to correct issues page
  • All example links on npm now correctly resolve to files in the graphql-request branch

Links

• npm package
• Full Changelog

v7.3.0: graphql-request v7.3.0

Compare Source

What's Changed

Features

• CommonJS Support: Added CommonJS module format () alongside ESM for better compatibility with Jest and other testing environments that aren't fully ESM-ready
• Improved Type Defaults: Default type parameters to any for easier migration and reduced type friction

Pull Requests

• feat(graphql-request): default types any and support common js #​1396

Contributors

Thanks to @​Moumouls (Antoine Cormouls) for the contribution! 🚀

---

Installation:

npm install graphql-request@7.3.0

Package: https://www.npmjs.com/package/graphql-request/v/7.3.0

v7.2.0: graphql-request@7.2.0

Compare Source

Features:

• Support GraphQL@​15 849c9ab

---

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Enabled.

♻ Rebasing: Whenever PR is behind base branch, 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.

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Preview	Comments	Updated (UTC)
2digits-blog-case	Error			Dec 12, 2025 5:12pm