@sanity/client 7.23.0 → 7.23.1

package/dist/stega.browser.d.cts

@@ -906,11 +906,26 @@ export declare function connectEventSource<EventName extends string>(
 
 /**
  * @public
- * Thrown if the EventSource connection could not be established.
- * Note that ConnectionFailedErrors are rare, and disconnects will normally be handled by the EventSource instance itself and emitted as `reconnect` events.
+ * Thrown when the EventSource connection could not be established, or was rejected by the server.
+ * Transient failures (network drops, 5xx, 408, 429) are reconnected internally and emitted as
+ * `reconnect` events; a permanent rejection (any other 4xx, eg an expired token) errors the
+ * stream with this class so consumers can react — check `status` for the rejection code.
  */
 export declare class ConnectionFailedError extends Error {
   readonly name = 'ConnectionFailedError'
+  /**
+   * HTTP status code of the rejected connection attempt, if known.
+   * Only set when the EventSource implementation exposes it — the polyfill used in
+   * Node.js and when custom headers (eg authorization) are required does, while
+   * native EventSource implementations (browser and Node.js) do not.
+   */
+  readonly status?: number
+  constructor(
+    message?: string,
+    options?: ErrorOptions & {
+      status?: number
+    },
+  )
 }
 
 /**

package/dist/stega.browser.d.ts

@@ -906,11 +906,26 @@ export declare function connectEventSource<EventName extends string>(
 
 /**
  * @public
- * Thrown if the EventSource connection could not be established.
- * Note that ConnectionFailedErrors are rare, and disconnects will normally be handled by the EventSource instance itself and emitted as `reconnect` events.
+ * Thrown when the EventSource connection could not be established, or was rejected by the server.
+ * Transient failures (network drops, 5xx, 408, 429) are reconnected internally and emitted as
+ * `reconnect` events; a permanent rejection (any other 4xx, eg an expired token) errors the
+ * stream with this class so consumers can react — check `status` for the rejection code.
  */
 export declare class ConnectionFailedError extends Error {
   readonly name = 'ConnectionFailedError'
+  /**
+   * HTTP status code of the rejected connection attempt, if known.
+   * Only set when the EventSource implementation exposes it — the polyfill used in
+   * Node.js and when custom headers (eg authorization) are required does, while
+   * native EventSource implementations (browser and Node.js) do not.
+   */
+  readonly status?: number
+  constructor(
+    message?: string,
+    options?: ErrorOptions & {
+      status?: number
+    },
+  )
 }
 
 /**

package/dist/stega.d.cts

@@ -906,11 +906,26 @@ export declare function connectEventSource<EventName extends string>(
 
 /**
  * @public
- * Thrown if the EventSource connection could not be established.
- * Note that ConnectionFailedErrors are rare, and disconnects will normally be handled by the EventSource instance itself and emitted as `reconnect` events.
+ * Thrown when the EventSource connection could not be established, or was rejected by the server.
+ * Transient failures (network drops, 5xx, 408, 429) are reconnected internally and emitted as
+ * `reconnect` events; a permanent rejection (any other 4xx, eg an expired token) errors the
+ * stream with this class so consumers can react — check `status` for the rejection code.
  */
 export declare class ConnectionFailedError extends Error {
   readonly name = 'ConnectionFailedError'
+  /**
+   * HTTP status code of the rejected connection attempt, if known.
+   * Only set when the EventSource implementation exposes it — the polyfill used in
+   * Node.js and when custom headers (eg authorization) are required does, while
+   * native EventSource implementations (browser and Node.js) do not.
+   */
+  readonly status?: number
+  constructor(
+    message?: string,
+    options?: ErrorOptions & {
+      status?: number
+    },
+  )
 }
 
 /**

package/dist/stega.d.ts

@@ -906,11 +906,26 @@ export declare function connectEventSource<EventName extends string>(
 
 /**
  * @public
- * Thrown if the EventSource connection could not be established.
- * Note that ConnectionFailedErrors are rare, and disconnects will normally be handled by the EventSource instance itself and emitted as `reconnect` events.
+ * Thrown when the EventSource connection could not be established, or was rejected by the server.
+ * Transient failures (network drops, 5xx, 408, 429) are reconnected internally and emitted as
+ * `reconnect` events; a permanent rejection (any other 4xx, eg an expired token) errors the
+ * stream with this class so consumers can react — check `status` for the rejection code.
  */
 export declare class ConnectionFailedError extends Error {
   readonly name = 'ConnectionFailedError'
+  /**
+   * HTTP status code of the rejected connection attempt, if known.
+   * Only set when the EventSource implementation exposes it — the polyfill used in
+   * Node.js and when custom headers (eg authorization) are required does, while
+   * native EventSource implementations (browser and Node.js) do not.
+   */
+  readonly status?: number
+  constructor(
+    message?: string,
+    options?: ErrorOptions & {
+      status?: number
+    },
+  )
 }
 
 /**

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@sanity/client",
-  "version": "7.23.0",
+  "version": "7.23.1",
   "description": "Client for retrieving, creating and patching data from Sanity.io",
   "keywords": [
     "sanity",

package/src/data/eventsource.ts

@@ -5,11 +5,25 @@ import {type Any} from '../types'
 
 /**
  * @public
- * Thrown if the EventSource connection could not be established.
- * Note that ConnectionFailedErrors are rare, and disconnects will normally be handled by the EventSource instance itself and emitted as `reconnect` events.
+ * Thrown when the EventSource connection could not be established, or was rejected by the server.
+ * Transient failures (network drops, 5xx, 408, 429) are reconnected internally and emitted as
+ * `reconnect` events; a permanent rejection (any other 4xx, eg an expired token) errors the
+ * stream with this class so consumers can react — check `status` for the rejection code.
  */
 export class ConnectionFailedError extends Error {
   readonly name = 'ConnectionFailedError'
+  /**
+   * HTTP status code of the rejected connection attempt, if known.
+   * Only set when the EventSource implementation exposes it — the polyfill used in
+   * Node.js and when custom headers (eg authorization) are required does, while
+   * native EventSource implementations (browser and Node.js) do not.
+   */
+  readonly status?: number
+  constructor(message?: string, options: ErrorOptions & {status?: number} = {}) {
+    const {status, ...errorOptions} = options
+    super(message, errorOptions)
+    this.status = status
+  }
 }
 
 /**
@@ -147,6 +161,18 @@ function connectWithESInstance<EventTypeName extends string>(
       // automatically, but in some cases (like when a laptop lid is closed), it will trigger onError
       // if it can't reconnect.
       // see https://html.spec.whatwg.org/multipage/server-sent-events.html#sse-processing-model
+      // The polyfills expose the HTTP status of a rejected connection on the error event
+      // (native EventSource implementations do not). A status means the server rejected the
+      // connection attempt, so error out regardless of readyState — the polyfills disagree
+      // on whether the connection closes before or after the error event is dispatched —
+      // and let `reconnectOnConnectionFailure` classify it (4xx fatal, otherwise retried).
+      const rawStatus = (evt as {status?: unknown}).status
+      const status = typeof rawStatus === 'number' ? rawStatus : undefined
+      if (status !== undefined) {
+        observer.error(new ConnectionFailedError('EventSource connection failed', {status}))
+        return
+      }
+
       if (es.readyState === es.CLOSED) {
         // In these cases we'll signal to consumers (via the error path) that a retry/reconnect is needed.
         observer.error(new ConnectionFailedError('EventSource connection failed'))

package/src/data/reconnectOnConnectionFailure.ts

@@ -11,6 +11,8 @@ import {
 
 import {ConnectionFailedError} from './eventsource'
 
+const RETRYABLE_STATUSES = new Set([408, 429])
+
 /**
  * Note: connection failure is not the same as network disconnect which may happen more frequent.
  * The EventSource instance will automatically reconnect in case of a network disconnect, however,
@@ -20,7 +22,19 @@ export function reconnectOnConnectionFailure<T>(): OperatorFunction<T, T | {type
   return function (source: Observable<T>) {
     return source.pipe(
       catchError((err, caught) => {
-        if (err instanceof ConnectionFailedError) {
+        // Only reconnect on transient connection failures. A 4xx response is a
+        // rejection, not a transient failure — the server will keep rejecting
+        // (eg an expired token), so reconnecting would loop forever. The named
+        // exceptions are the explicitly transient 4xx statuses: 408 (request
+        // timeout) and 429 (rate limited). Anything else surfaces to the
+        // consumer instead.
+        if (
+          err instanceof ConnectionFailedError &&
+          (typeof err.status !== 'number' ||
+            err.status < 400 ||
+            err.status >= 500 ||
+            RETRYABLE_STATUSES.has(err.status))
+        ) {
           return concat(of({type: 'reconnect' as const}), timer(1000).pipe(mergeMap(() => caught)))
         }
         return throwError(() => err)

package/umd/sanityClient.js

@@ -2406,6 +2406,17 @@ ${codeFrame(query, { start, end }, description)}${withTag}${withTraceId}`;
   };
   class ConnectionFailedError extends Error {
     name = "ConnectionFailedError";
+    /**
+     * HTTP status code of the rejected connection attempt, if known.
+     * Only set when the EventSource implementation exposes it — the polyfill used in
+     * Node.js and when custom headers (eg authorization) are required does, while
+     * native EventSource implementations (browser and Node.js) do not.
+     */
+    status;
+    constructor(message, options = {}) {
+      const { status, ...errorOptions } = options;
+      super(message, errorOptions), this.status = status;
+    }
   }
   class DisconnectError extends Error {
     name = "DisconnectError";
@@ -2449,6 +2460,11 @@ ${codeFrame(query, { start, end }, description)}${withTag}${withTraceId}`;
           );
           return;
         }
+        const rawStatus = evt.status, status = typeof rawStatus == "number" ? rawStatus : void 0;
+        if (status !== void 0) {
+          observer.error(new ConnectionFailedError("EventSource connection failed", { status }));
+          return;
+        }
         es.readyState === es.CLOSED ? observer.error(new ConnectionFailedError("EventSource connection failed")) : emitReconnect && observer.next({ type: "reconnect" });
       }
       function onOpen() {
@@ -3418,11 +3434,11 @@ ${selectionOpts}`);
   const pick = (obj, props) => props.reduce((selection, prop) => (typeof obj[prop] > "u" || (selection[prop] = obj[prop]), selection), {}), eventSourcePolyfill = defer(() => Promise.resolve().then(function () { return browser$1; })).pipe(
     map(({ default: EventSource2 }) => EventSource2),
     shareReplay(1)
-  );
+  ), RETRYABLE_STATUSES = /* @__PURE__ */ new Set([408, 429]);
   function reconnectOnConnectionFailure() {
     return function(source) {
       return source.pipe(
-        catchError((err, caught) => err instanceof ConnectionFailedError ? concat(of({ type: "reconnect" }), timer(1e3).pipe(mergeMap(() => caught))) : throwError(() => err))
+        catchError((err, caught) => err instanceof ConnectionFailedError && (typeof err.status != "number" || err.status < 400 || err.status >= 500 || RETRYABLE_STATUSES.has(err.status)) ? concat(of({ type: "reconnect" }), timer(1e3).pipe(mergeMap(() => caught))) : throwError(() => err))
       );
     };
   }