Fixes #7889
Fixes #7715

Summary

• Fix "Unexpected end of JSON input" error at client.gen.ts:167 when server returns empty response body

Root Cause

Two issues causing the JSON parsing error:

1. Server-side: OPTIONS handler in /packages/console/app/src/routes/zen/v1/models.ts returned status: 200 with null body
2. Client-side: SDK only handled empty responses with status: 204 or Content-Length: "0", but didn't handle empty body with 200 status and no Content-Length header

Changes

Server (packages/console/app/src/routes/zen/v1/models.ts)

• Changed OPTIONS response from status: 200 → status: 204 (proper "No Content" status)

SDK Client (both v1 and v2 client.gen.ts)

• Read response as text first, only parse JSON if non-empty
• Added try-catch with contextual error messages for malformed JSON:

case "json": {
  const text = await response.text()
  if (!text) {
    data = {}
  } else {
    try {
      data = JSON.parse(text)
    } catch (parseError) {
      const errorMessage = parseError instanceof Error ? parseError.message : String(parseError)
      throw new Error(
        `Failed to parse JSON response: ${errorMessage}. Status: ${response.status}, URL: ${response.url}`
      )
    }
  }
  break
}

Comparison with #7618

This PR prevents the crash entirely AND provides good error messages for actual malformed JSON.

Note

These files are auto-generated by @hey-api/openapi-ts. This fix will need to be reapplied after regeneration, or ideally contributed upstream to @hey-api/client-fetch.