@doist/comms-sdk 2.0.0 → 2.0.2

package/dist/cjs/clients/conversations-client.js

@@ -143,7 +143,7 @@ class ConversationsClient extends base_client_1.BaseClient {
      * @returns The updated conversation object.
      */
     archiveConversation(id) {
-        return this.simple('GET', 'archive', { id }, this.conversationSchema);
+        return this.simple('POST', 'archive', { id }, this.conversationSchema);
     }
     /**
      * Unarchives a conversation.
@@ -152,7 +152,7 @@ class ConversationsClient extends base_client_1.BaseClient {
      * @returns The updated conversation object.
      */
     unarchiveConversation(id) {
-        return this.simple('GET', 'unarchive', { id }, this.conversationSchema);
+        return this.simple('POST', 'unarchive', { id }, this.conversationSchema);
     }
     /**
      * Adds a user to a conversation.

package/dist/cjs/utils/multipart-upload.js

@@ -2,6 +2,7 @@
 Object.defineProperty(exports, "__esModule", { value: true });
 exports.getContentTypeFromFileName = getContentTypeFromFileName;
 exports.uploadMultipartFile = uploadMultipartFile;
+const uuid_1 = require("uuid");
 const fetch_with_retry_1 = require("../transport/fetch-with-retry");
 /**
  * Determine a content-type from a filename extension. Falls back to
@@ -71,8 +72,7 @@ const MIME_BY_EXTENSION = {
 };
 /**
  * Normalise a supported {@link UploadFile} into a `Blob` plus a resolved file name and
- * content type, so uploads use the cross-platform global `FormData`/`Blob` body that
- * `undici` and browsers both accept natively.
+ * content type, ready to be encoded into the multipart body.
  */
 function toBlob(file, fileName, contentType) {
     if (file instanceof Blob) {
@@ -97,15 +97,72 @@ function toBlob(file, fileName, contentType) {
     }
     throw new Error('Unsupported file type for upload: expected a Blob or Uint8Array');
 }
+/**
+ * Escapes a value for use inside a quoted `Content-Disposition` parameter, where a raw
+ * quote would end the value early and a raw CR or LF would end the header. A lone CR
+ * needs escaping too, not just CRLF pairs.
+ *
+ * This is the same escaping the platform's own `FormData` encoder applies, so servers
+ * see exactly what they would from any browser.
+ */
+function escapeDispositionValue(value) {
+    return value.replace(/"/g, '%22').replace(/\r/g, '%0D').replace(/\n/g, '%0A');
+}
+/**
+ * Rejects a media type that could not be safely written into a part header.
+ *
+ * `contentType` is public caller input and reaches the header verbatim. A value
+ * carrying a CR or LF would end the header early and let the caller forge one
+ * of its own — `Blob` normalises the `type` it stores, but the supplied value
+ * is what gets interpolated. Reject rather than silently rewrite, so a caller
+ * passing something unusable finds out instead of having it altered.
+ */
+function assertHeaderSafeContentType(contentType) {
+    if (!/^[\x20-\x7e]*$/.test(contentType)) {
+        throw new Error('contentType must contain only printable ASCII characters, without CR or LF');
+    }
+}
+/**
+ * Encodes a `multipart/form-data` body as a `Blob`, together with the `Content-Type`
+ * that describes it.
+ *
+ * Deliberately avoids `FormData`. A `FormData` body is only encoded by the `fetch` that
+ * owns that `FormData` class — undici brands its own and checks it with a plain
+ * `instanceof` — and the SDK dispatches through undici's own `fetch` to keep the request
+ * client on the same undici as the dispatcher. A global `FormData` handed to it is
+ * stringified to the literal `"[object FormData]"`, so the upload silently carries no
+ * file. `Blob` has no such brand and works with whichever `fetch` sends the request,
+ * including a caller-supplied `customFetch`.
+ */
+function buildMultipartBody(args) {
+    const { blob, fileName, contentType, fields } = args;
+    assertHeaderSafeContentType(contentType);
+    const boundary = `----comms-sdk-${(0, uuid_1.v4)()}`;
+    const parts = [
+        `--${boundary}\r\n` +
+            `Content-Disposition: form-data; name="file"; filename="${escapeDispositionValue(fileName)}"\r\n` +
+            `Content-Type: ${contentType}\r\n\r\n`,
+        blob,
+        '\r\n',
+    ];
+    for (const [key, value] of Object.entries(fields)) {
+        if (value !== undefined && value !== null) {
+            parts.push(`--${boundary}\r\n` +
+                `Content-Disposition: form-data; name="${escapeDispositionValue(key)}"\r\n\r\n` +
+                `${String(value)}\r\n`);
+        }
+    }
+    parts.push(`--${boundary}--\r\n`);
+    return { body: new Blob(parts), contentType: `multipart/form-data; boundary=${boundary}` };
+}
 /**
  * Upload a file using `multipart/form-data`.
  *
- * Builds the request body with the global `FormData`/`Blob` so it works unchanged in the
- * browser and in Node.js (via `undici`). The `file` part is sent alongside `file_name`,
+ * Encodes the request body as a `Blob` so it works unchanged in the browser and in
+ * Node.js, whichever `fetch` ends up sending it. The `file` part is sent alongside `file_name`,
  * `file_size`, and `underlying_type` fields (the canonical Comms upload shape); any
  * `additionalFields` are merged in and override the derived values. Authentication uses
- * `Authorization: Bearer`, matching every other Comms SDK client, and `Content-Type` is
- * intentionally left unset so the runtime adds the correct multipart boundary.
+ * `Authorization: Bearer`, matching every other Comms SDK client.
  *
  * The response is JSON-parsed and camel-cased by {@link fetchWithRetry}; callers validate
  * the returned shape with the appropriate schema.
@@ -119,15 +176,17 @@ async function uploadMultipartFile(args) {
         underlying_type: resolvedType,
         ...additionalFields,
     };
-    const form = new FormData();
-    form.append('file', blob, resolvedFileName);
-    for (const [key, value] of Object.entries(fields)) {
-        if (value !== undefined && value !== null) {
-            form.append(key, String(value));
-        }
-    }
+    const multipart = buildMultipartBody({
+        blob,
+        fileName: resolvedFileName,
+        contentType: resolvedType,
+        fields,
+    });
     const headers = {
         Authorization: `Bearer ${authToken}`,
+        // The boundary is ours, so this has to be declared explicitly — `fetch`
+        // only fills it in for a `FormData` body.
+        'Content-Type': multipart.contentType,
     };
     if (requestId) {
         headers['X-Request-Id'] = requestId;
@@ -136,8 +195,7 @@ async function uploadMultipartFile(args) {
     const response = await (0, fetch_with_retry_1.fetchWithRetry)(url, {
         method: 'POST',
         headers,
-        body: form,
-        // Don't set Content-Type — the runtime adds the multipart boundary.
+        body: multipart.body,
         timeout: 30000,
     }, maxRetries, customFetch);
     return response.data;

package/dist/esm/clients/conversations-client.js

@@ -140,7 +140,7 @@ export class ConversationsClient extends BaseClient {
      * @returns The updated conversation object.
      */
     archiveConversation(id) {
-        return this.simple('GET', 'archive', { id }, this.conversationSchema);
+        return this.simple('POST', 'archive', { id }, this.conversationSchema);
     }
     /**
      * Unarchives a conversation.
@@ -149,7 +149,7 @@ export class ConversationsClient extends BaseClient {
      * @returns The updated conversation object.
      */
     unarchiveConversation(id) {
-        return this.simple('GET', 'unarchive', { id }, this.conversationSchema);
+        return this.simple('POST', 'unarchive', { id }, this.conversationSchema);
     }
     /**
      * Adds a user to a conversation.

package/dist/esm/utils/multipart-upload.js

@@ -1,3 +1,4 @@
+import { v4 as uuid } from 'uuid';
 import { fetchWithRetry } from '../transport/fetch-with-retry.js';
 /**
  * Determine a content-type from a filename extension. Falls back to
@@ -67,8 +68,7 @@ const MIME_BY_EXTENSION = {
 };
 /**
  * Normalise a supported {@link UploadFile} into a `Blob` plus a resolved file name and
- * content type, so uploads use the cross-platform global `FormData`/`Blob` body that
- * `undici` and browsers both accept natively.
+ * content type, ready to be encoded into the multipart body.
  */
 function toBlob(file, fileName, contentType) {
     if (file instanceof Blob) {
@@ -93,15 +93,72 @@ function toBlob(file, fileName, contentType) {
     }
     throw new Error('Unsupported file type for upload: expected a Blob or Uint8Array');
 }
+/**
+ * Escapes a value for use inside a quoted `Content-Disposition` parameter, where a raw
+ * quote would end the value early and a raw CR or LF would end the header. A lone CR
+ * needs escaping too, not just CRLF pairs.
+ *
+ * This is the same escaping the platform's own `FormData` encoder applies, so servers
+ * see exactly what they would from any browser.
+ */
+function escapeDispositionValue(value) {
+    return value.replace(/"/g, '%22').replace(/\r/g, '%0D').replace(/\n/g, '%0A');
+}
+/**
+ * Rejects a media type that could not be safely written into a part header.
+ *
+ * `contentType` is public caller input and reaches the header verbatim. A value
+ * carrying a CR or LF would end the header early and let the caller forge one
+ * of its own — `Blob` normalises the `type` it stores, but the supplied value
+ * is what gets interpolated. Reject rather than silently rewrite, so a caller
+ * passing something unusable finds out instead of having it altered.
+ */
+function assertHeaderSafeContentType(contentType) {
+    if (!/^[\x20-\x7e]*$/.test(contentType)) {
+        throw new Error('contentType must contain only printable ASCII characters, without CR or LF');
+    }
+}
+/**
+ * Encodes a `multipart/form-data` body as a `Blob`, together with the `Content-Type`
+ * that describes it.
+ *
+ * Deliberately avoids `FormData`. A `FormData` body is only encoded by the `fetch` that
+ * owns that `FormData` class — undici brands its own and checks it with a plain
+ * `instanceof` — and the SDK dispatches through undici's own `fetch` to keep the request
+ * client on the same undici as the dispatcher. A global `FormData` handed to it is
+ * stringified to the literal `"[object FormData]"`, so the upload silently carries no
+ * file. `Blob` has no such brand and works with whichever `fetch` sends the request,
+ * including a caller-supplied `customFetch`.
+ */
+function buildMultipartBody(args) {
+    const { blob, fileName, contentType, fields } = args;
+    assertHeaderSafeContentType(contentType);
+    const boundary = `----comms-sdk-${uuid()}`;
+    const parts = [
+        `--${boundary}\r\n` +
+            `Content-Disposition: form-data; name="file"; filename="${escapeDispositionValue(fileName)}"\r\n` +
+            `Content-Type: ${contentType}\r\n\r\n`,
+        blob,
+        '\r\n',
+    ];
+    for (const [key, value] of Object.entries(fields)) {
+        if (value !== undefined && value !== null) {
+            parts.push(`--${boundary}\r\n` +
+                `Content-Disposition: form-data; name="${escapeDispositionValue(key)}"\r\n\r\n` +
+                `${String(value)}\r\n`);
+        }
+    }
+    parts.push(`--${boundary}--\r\n`);
+    return { body: new Blob(parts), contentType: `multipart/form-data; boundary=${boundary}` };
+}
 /**
  * Upload a file using `multipart/form-data`.
  *
- * Builds the request body with the global `FormData`/`Blob` so it works unchanged in the
- * browser and in Node.js (via `undici`). The `file` part is sent alongside `file_name`,
+ * Encodes the request body as a `Blob` so it works unchanged in the browser and in
+ * Node.js, whichever `fetch` ends up sending it. The `file` part is sent alongside `file_name`,
  * `file_size`, and `underlying_type` fields (the canonical Comms upload shape); any
  * `additionalFields` are merged in and override the derived values. Authentication uses
- * `Authorization: Bearer`, matching every other Comms SDK client, and `Content-Type` is
- * intentionally left unset so the runtime adds the correct multipart boundary.
+ * `Authorization: Bearer`, matching every other Comms SDK client.
  *
  * The response is JSON-parsed and camel-cased by {@link fetchWithRetry}; callers validate
  * the returned shape with the appropriate schema.
@@ -115,15 +172,17 @@ export async function uploadMultipartFile(args) {
         underlying_type: resolvedType,
         ...additionalFields,
     };
-    const form = new FormData();
-    form.append('file', blob, resolvedFileName);
-    for (const [key, value] of Object.entries(fields)) {
-        if (value !== undefined && value !== null) {
-            form.append(key, String(value));
-        }
-    }
+    const multipart = buildMultipartBody({
+        blob,
+        fileName: resolvedFileName,
+        contentType: resolvedType,
+        fields,
+    });
     const headers = {
         Authorization: `Bearer ${authToken}`,
+        // The boundary is ours, so this has to be declared explicitly — `fetch`
+        // only fills it in for a `FormData` body.
+        'Content-Type': multipart.contentType,
     };
     if (requestId) {
         headers['X-Request-Id'] = requestId;
@@ -132,8 +191,7 @@ export async function uploadMultipartFile(args) {
     const response = await fetchWithRetry(url, {
         method: 'POST',
         headers,
-        body: form,
-        // Don't set Content-Type — the runtime adds the multipart boundary.
+        body: multipart.body,
         timeout: 30000,
     }, maxRetries, customFetch);
     return response.data;

package/dist/types/utils/multipart-upload.d.ts

@@ -44,12 +44,11 @@ export declare function getContentTypeFromFileName(fileName: string): string;
 /**
  * Upload a file using `multipart/form-data`.
  *
- * Builds the request body with the global `FormData`/`Blob` so it works unchanged in the
- * browser and in Node.js (via `undici`). The `file` part is sent alongside `file_name`,
+ * Encodes the request body as a `Blob` so it works unchanged in the browser and in
+ * Node.js, whichever `fetch` ends up sending it. The `file` part is sent alongside `file_name`,
  * `file_size`, and `underlying_type` fields (the canonical Comms upload shape); any
  * `additionalFields` are merged in and override the derived values. Authentication uses
- * `Authorization: Bearer`, matching every other Comms SDK client, and `Content-Type` is
- * intentionally left unset so the runtime adds the correct multipart boundary.
+ * `Authorization: Bearer`, matching every other Comms SDK client.
  *
  * The response is JSON-parsed and camel-cased by {@link fetchWithRetry}; callers validate
  * the returned shape with the appropriate schema.

package/package.json

@@ -1,6 +1,6 @@
 {
     "name": "@doist/comms-sdk",
-    "version": "2.0.0",
+    "version": "2.0.2",
     "description": "A TypeScript wrapper for the Comms REST API.",
     "author": "Doist developers",
     "homepage": "https://doist.github.io/comms-sdk-typescript/",