@procedures/client 0.41.0 → 0.42.0

package/src/client/errors/registry.ts

@@ -168,6 +168,19 @@ const DESCRIBED_ERRORS = {
     ],
   }),
 
+  // The end of an NDJSON stream of HttpTransport without its done line or its error line. The
+  // HTTP client gives this code, and no server sends it.
+  STREAM_ENDED: defineError(ErrorCode.STREAM_ENDED, {
+    summary: "The stream ended without its end line",
+    detail: "The NDJSON stream of the response ended without a done line and without an error line. The connection broke during the stream.",
+    category: ErrorCategory.NETWORK,
+    retryable: true,
+    severity: ErrorSeverity.WARNING,
+    userMessage: "The connection broke during the response. Try again.",
+    devMessage: "The body of an NDJSON response ended before its done line. The delivery is indeterminate: the call can have had its effect.",
+    suggestions: ["Retry only a call that is idempotent", "Find what closes the connection, for example a proxy"],
+  }),
+
   //
   // ═══ Timeout Errors ═══
   //
@@ -420,6 +433,19 @@ const DESCRIBED_ERRORS = {
     ],
   }),
 
+  // The refusal of HttpTransport for metadata above the limit of the X-Metadata header. The
+  // request does not go, so the entry has no HTTP status.
+  METADATA_TOO_LARGE: defineError(ErrorCode.METADATA_TOO_LARGE, {
+    summary: "The metadata is too large for a header",
+    detail: "The metadata of the call is longer than the limit of the X-Metadata header, 8192 characters. The HTTP client did not send the request.",
+    category: ErrorCategory.CLIENT,
+    retryable: false,
+    severity: ErrorSeverity.ERROR,
+    userMessage: "The request has too much metadata.",
+    devMessage: "The URI-encoded JSON of the custom metadata keys is longer than METADATA_HEADER_LIMIT. Send the large values in the input.",
+    suggestions: ["Put the large values in the input of the call", "Remove the metadata keys that the server does not read"],
+  }),
+
   UNPROCESSABLE_ENTITY: defineError(ErrorCode.UNPROCESSABLE_ENTITY, {
     summary: "Unprocessable entity",
     detail: "The request is well-formed but contains semantic errors.",

package/src/client/index.ts

@@ -24,7 +24,7 @@ export {
 
 // Transport Adapters
 export { HttpTransport, defaultUrlPattern, restfulHttpMethodStrategy, postOnlyStrategy } from "../adapters/http/client/index.js";
-export type { HttpTransportOptions, UrlStrategy, HttpMethodStrategy } from "../adapters/http/client/index.js";
+export type { HttpTransportOptions, HttpBatchOptions, UrlStrategy, HttpMethodStrategy } from "../adapters/http/client/index.js";
 
 export { LocalTransport } from "../adapters/local/client/index.js";
 export type { LocalTransportOptions, Handler } from "../adapters/local/client/index.js";

package/src/node.ts

@@ -32,6 +32,8 @@ export { procedureHandler } from "./adapters/http/server/handler.js";
 // The JSON body of a request, read to a limit: the procedure handler and the MCP face read it so (CLI-35)
 export { readJsonBody, BodyError } from "./adapters/http/server/body.js";
 export type { ProcedureHandlerOptions, NodeProcedureHandler, NodeUrlStrategy, UrlRequest } from "./adapters/http/server/handler.js";
+// The batches of calls of the procedure handler (CLI-32)
+export type { HandlerBatchOptions } from "./adapters/http/server/batch.js";
 export type { CorsOptions, CredentialedCorsOptions } from "./adapters/http/server/cors.js";
 // The credentialed CORS of the trusted origins of a host, for a route of the app (CLI-49)
 export { credentialedCors } from "./adapters/http/server/cors.js";