@backblaze-labs/b2-sdk - v0.2.0
    Preparing search index...

    Variable KNOWN_B2_ERROR_CODESConst

    KNOWN_B2_ERROR_CODES: readonly [
        "expired_auth_token",
        "bad_auth_token",
        "unauthorized",
        "bad_request",
        "bad_bucket_name",
        "bad_bucket_id",
        "not_found",
        "method_not_allowed",
        "request_timeout",
        "too_many_requests",
        "conflict",
        "duplicate_bucket_name",
        "too_many_buckets",
        "too_many_files",
        "cap_exceeded",
        "storage_cap_exceeded",
        "transaction_cap_exceeded",
        "download_cap_exceeded",
        "access_denied",
        "service_unavailable",
        "internal_error",
        "bad_json",
        "invalid_bucket_id",
        "invalid_bucket_name",
        "invalid_bucket_info",
        "file_not_present",
        "no_such_file",
        "out_of_range",
        "range_not_satisfiable",
        "invalid_file_id",
        "invalid_file_name",
        "invalid_file_info",
        "invalid_part_number",
        "bad_sha1_checksum",
    ] = ...

    B2 API error codes documented by the SDK. This list drives KnownB2ErrorCode; B2ErrorCode adds a string fallback so callers can receive unknown future server codes while keeping autocomplete for known values.