Fetch Client API Documentation - v1.1.1
    Preparing search index...

    Variable ERROR_CODESConst Readonly

    ERROR_CODES: {
        HTTP_ERROR: "HTTP_ERROR";
        TIMEOUT: "TIMEOUT";
        NETWORK_ERROR: "NETWORK_ERROR";
        ABORTED: "ABORTED";
        JSON_PARSE_ERROR: "JSON_PARSE_ERROR";
        TEXT_PARSE_ERROR: "TEXT_PARSE_ERROR";
        BLOB_PARSE_ERROR: "BLOB_PARSE_ERROR";
        ARRAYBUFFER_PARSE_ERROR: "ARRAYBUFFER_PARSE_ERROR";
        UNKNOWN_ERROR: "UNKNOWN_ERROR";
    } = ...

    Error codes used throughout the API client

    Type Declaration

    • ReadonlyHTTP_ERROR: "HTTP_ERROR"

      HTTP error - server returned 4xx or 5xx status

    • ReadonlyTIMEOUT: "TIMEOUT"

      Timeout error - request exceeded time limit

    • ReadonlyNETWORK_ERROR: "NETWORK_ERROR"

      Network error - connectivity or DNS issues

    • ReadonlyABORTED: "ABORTED"

      Aborted error - request was manually cancelled

    • ReadonlyJSON_PARSE_ERROR: "JSON_PARSE_ERROR"

      JSON parsing error - invalid JSON response

    • ReadonlyTEXT_PARSE_ERROR: "TEXT_PARSE_ERROR"

      Text parsing error - failed to read as text

    • ReadonlyBLOB_PARSE_ERROR: "BLOB_PARSE_ERROR"

      Blob parsing error - failed to read as blob

    • ReadonlyARRAYBUFFER_PARSE_ERROR: "ARRAYBUFFER_PARSE_ERROR"

      ArrayBuffer parsing error - failed to read as buffer

    • ReadonlyUNKNOWN_ERROR: "UNKNOWN_ERROR"

      Unknown error - unexpected error type

    Standardized error codes for consistent error handling and debugging across the entire client library.

    // Create specific error types
    throw new ApiError(ERROR_CODES.TIMEOUT, 408, 'Request timed out');

    // Handle different error types
    switch (error.code) {
      case ERROR_CODES.NETWORK_ERROR:
        // Handle network issues
        break;
      case ERROR_CODES.HTTP_ERROR:
        // Handle HTTP errors
        break;
    }

    Settings

    Member Visibility