fix(client): handle top-level large integer JSON values

polaz · polaz · commit 286004124e5a · 2026-01-16T16:37:01.000+02:00
Address review feedback:
- Add TOP_LEVEL_LARGE_INT pattern for bare scalar integers
- Return string directly when JSON is just a large integer
- Add regression test for top-level large integers

This handles edge cases like JSON columns storing numeric scalars.
diff --git a/packages/client-engine-runtime/src/utils.test.ts b/packages/client-engine-runtime/src/utils.test.ts
@@ -15,6 +15,12 @@ describe('safeJsonParse', () => {
     })
   })
 
+  test('handles top-level large integer JSON values', () => {
+    // JSON can be a bare scalar value (e.g., JSON columns storing numeric scalars)
+    expect(safeJsonParse('312590077454712834')).toBe('312590077454712834')
+    expect(safeJsonParse('-312590077454712834')).toBe('-312590077454712834')
+  })
+
   test('preserves 15-digit integers as numbers (safe)', () => {
     // 15-digit integers are always safe
     expect(safeJsonParse('{"id":123456789012345}')).toEqual({ id: 123456789012345 })
diff --git a/packages/client-engine-runtime/src/utils.ts b/packages/client-engine-runtime/src/utils.ts
@@ -149,6 +149,12 @@ const LARGE_INT_PATTERN = /("(?:[^"\\]|\\.)*")|(:\s*|[,\[]\s*)(-?\d{16,})(?=\s*[
  */
 const HAS_LARGE_INT = /\d{16}/
 
+/**
+ * Pattern to match a top-level large integer (JSON can be a bare scalar value).
+ * Handles cases like JSON columns storing numeric scalars.
+ */
+const TOP_LEVEL_LARGE_INT = /^-?\d{16,}$/
+
 /**
  * `JSON.parse` wrapper that preserves precision for large integer values.
  *
@@ -170,6 +176,12 @@ export function safeJsonParse(json: string): unknown {
     return JSON.parse(json)
   }
 
+  // Handle top-level large integers (JSON can be a bare scalar value).
+  // The main regex only matches integers after :, ,, or [ so this case needs special handling.
+  if (TOP_LEVEL_LARGE_INT.test(json)) {
+    return json
+  }
+
   // Slow path: replace large integers with quoted strings to preserve precision.
   // Numbers with 16+ digits may exceed MAX_SAFE_INTEGER and lose precision.
   // The regex has two alternatives: string literals (group 1) and integers (groups 2-3).
