Fix shouldRetry not retrying QuickNode's -32007 rate-limit code

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>

Author: Eras256

.changeset/fix-quicknode-retry.md

@@ -0,0 +1,5 @@
+---
+"viem": patch
+---
+
+Fixed `shouldRetry` not retrying QuickNode's `-32007` rate-limit error code, mirroring the existing handling for the `429` (Alchemy) case.

src/utils/buildRequest.test.ts

@@ -1544,6 +1544,19 @@ describe('shouldRetry', () => {
     expect(shouldRetry(err)).toBe(true)
   })
 
+  test('RPC code -32007 (QuickNode rate limit)', () => {
+    // QuickNode returns its own rate-limit error as `{ code: -32007 }`
+    // rather than the standard `LimitExceededRpcError` code (`-32005`) or
+    // HTTP 429. shouldRetry must return true so that retryCount is honoured.
+    const err = Object.assign(
+      new Error(
+        '15/second request limit reached - reduce calls per second or upgrade your account at quicknode.com',
+      ),
+      { code: -32007 },
+    )
+    expect(shouldRetry(err)).toBe(true)
+  })
+
   test('WalletConnectSessionSettlementError', () => {
     expect(
       shouldRetry(new WalletConnectSessionSettlementError({} as any)),

src/utils/buildRequest.ts

@@ -298,6 +298,12 @@ export function shouldRetry(error: Error) {
     // HTTP 200 with a JSON-RPC body of `{ code: 429 }` instead of an HTTP 429,
     // so we need to handle this code in addition to the HTTP status check below.
     if (error.code === 429) return true
+    // Request limit exceeded — QuickNode's own non-standard rate-limit code,
+    // distinct from the standard `LimitExceededRpcError` (`-32005`). Seen in
+    // production as `{ code: -32007, message: "N/second request limit
+    // reached - reduce calls per second or upgrade your account at
+    // quicknode.com" }`.
+    if (error.code === -32007) return true
     return false
   }
   if (error instanceof HttpRequestError && error.status) {